The following article describes various AvailabilityGuard database errors and how they can be resolved:
- ORA-01654 | ORA-01653 | ORA-30036: unable to extend index / table / segment .. in tablespace ts
- ORA-01652: unable to extend temp segment by n bytes in tablespace TEMP
- ORA-04030: out of process memory when trying to allocate nbytes (sort subheap,sort key)
- ORA-01950: no privileges on tablespace 'USERS'
Important Note: Database errors will impact the AvailabilityGuard system availability, and can be identified by reviewing AvailabilityGuard log files.
ORA-01654 | ORA-01653 | ORA-30036: unable to extend index / table / segment .. in tablespace ts
This error message means that the reported tablespace has no available free space. To resolve this error, add a data file to the tablespace.
The following Oracle command can be used to add a data file (dba rights required):
ALTER TABLESPACE ts
ADD DATAFILE
'D:\oracle\oradata\rgdb\ts02.dbf'
SIZE 5G
NEXT 5G
AUTOEXTEND ON
NOTE: Folder paths, sizes, file, tablespace and user names should be changed according to your database installation.
ORA-01652: unable to extend temp segment by n bytes in tablespace TEMP
This error message means that the TEMP tablespace has no available free space. To resolve this error, add a temp file to the tablespace.
The following Oracle command can be used to add a tempfile (dba rights required):
ALTER TABLESPACE TEMP
ADD TEMPFILE 'D:\oracle\oradata\rgdb\temp02.dbf'
SIZE 5G REUSE
AUTOEXTEND ON
NEXT 1G
ORA-04030: out of process memory when trying to allocate nbytes (sort subheap,sort key)
This error message means that the Oracle PGA memory allocation is insufficient. Resolution steps depend on whether Oracle AMM is used. Before making any changes, take particular care to backup the database ORACLE_HOME\database\SPFILEdbname.ORA file as incorrect changes may lead to failures to start the databases.
To find out if AMM is used, login through sqlplus to Oracle as dba and run the following command:
SHOW PARAMETER TARGET
If the output shows that memory_target is set to a non-zero value, you can conclude that AMM is used.
Increasing PGA when AMM is not used
ALTER SYSTEM SET pga_aggregate_target=nM SCOPE=BOTH;
Where n is the new size in MB.
Increasing PGA when AMM is used (database restart required)
ALTER SYSTEM SET memory_max_target=nG scope=spfile;
ALTER SYSTEM SET memory_target=nG scope=spfile;
SHUTDOWN ABORT;
STARTUP;
Where n is the new size in GB.
NOTE: If available memory is limited, consider also configuring SGA_MAX_SIZE when AMM is used to ensure PGA availability.
ORA-01950: no privileges on tablespace 'USERS'
This error may occur when quotas are configured for the AvailabilityGuard database user. To resolve it, run the following command logged in as sysdba:
ALTER USER USERNAME QUOTA UNLIMITED ON USERS;
Comments
0 comments
Please sign in to leave a comment.