Reply from Waelz, Dean on Mar 3 at 11:17 AM Good Day
The create command quoted below, specified the initial size of the data file (i.e. 'SIZE 20000M' ) at 20 GB. The autoextend option (when enabled) permits that DB file to increase in size. It will increase (when it needs to) by 20 MB increments (i.e. 'NEXT 20M' ), up to a max file size of 32 GB (i.e. 'MAXSIZE 32700M' ). If (for whatever reason) you don't want the DB files to get larger than they were when they got created (and assuming AUTOEXTEND is off), then you'll have to take action to add more of them (as required). The filesystem/block size will limit how large any given file can become (this is why you'll always want to set an appropriate DB file size limit with MAXSIZE, assuming AUTOEXTEND is enabled).
http://www.dba-oracle.com/t_undo_tablespce_alter_autoextend.htm
http://www.dba-oracle.com/t_alter_autoextend_on.htm
https://docs.oracle.com/cd/B28359_01/server.111/b2 8310/dfiles003.htm
https://docs.oracle.com/cd/B19306_01/server.102/b1 4231/undo.htm or https://docs.oracle.com/cd/B28359_01/server.111/b2 8310/undo005.htm
http://scn.sap.com/thread/186186
http://scn.sap.com/thread/3521955
Regards,
| | | ---------------Original Message---------------
From: bmacmillan
Sent: Thursday, March 03, 2016 9:27 AM
Subject: Proper Usage/Configuration Of PSAPUNDO
Good morning,
I hope someone can help me with some advice.
A while back, we started having issues in SAP, and traced it back to the PSAPUNDO tablespace being full.
Since then, we have been monitoring it, and adding datafiles as needed,
I now have a bit more time to look into this properly, and I discovered that when the PSAPUNDO tablespace was initially created (when we went live with ECC 6.0), the consultant created the datafiles using the "autoextend" option.
See below:
CREATE UNDO TABLESPACE PSAPUNDO DATAFILE '/oracle/PRD/sapdata1/undo_1/undo.data1' SIZE 20000M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 32700M
Sat Apr 12 17:21:40 2014
[21306] Successfully onlined Undo Tablespace 2.
Completed: CREATE UNDO TABLESPACE PSAPUNDO DATAFILE '/oracle/PRD/sapdata1/undo_1/undo.data1' SIZE 20000M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 32700M
ALTER TABLESPACE PSAPUNDO ADD DATAFILE
'/oracle/PRD/sapdata2/undo_2/undo.data2' SIZE 32000M AUTOEXTEND ON NEXT 20M MAXSIZE 32700M,
'/oracle/PRD/sapdata3/undo_3/undo.data3' SIZE 32000M AUTOEXTEND ON NEXT 20M MAXSIZE 32700M,
'/oracle/PRD/sapdata4/undo_4/undo.data4' SIZE 32000M AUTOEXTEND ON NEXT 20M MAXSIZE 32700M
Now, when we first experienced the issues, we added new datafiles without using the "autoextend" option (we didn't know any better), but when I added the last 4, I started using the option again:
My question is - what, exactly, does the autoextend option do for us?
I was under the impression that this would ensure that datafiles would get added automatically, as required. But, if that is the case, why did we all of a sudden start to need to add datafiles, given the manner in which our consultant created the initial datafiles within PSAPUNDO?
Note that we have never needed to add datafiles, manually, to any of the other tablespaces - they have been added automatically, as we'd expect.
Please explain, if you can. Or, let me know if you need more information.
Thanks,
Bruce
. |
| Reply to this email to post your response. __.____._ |    _.____.__ |
