on 05-07-2008 8:53 AM
Hello,
SAP Release : ECC6
Oracle 10g (Locally Managed Tablespace)
Sun Solaris 10 X86
We just have performed an homogeneous system copy from our production environnement PMA to our sandbox BMA.
All the post copy actions have been done ( delete entries from tables, se06, bdls, etc ...)
The SAP instance is now working correctly.
Afterwards, I've tried to perform a database check either using the DB13 action "Check database" or
directly from the command line : "brconnect -u / -c -f check"
Either way, I'm getting hundreds of error messages :
ORA-1653: unable to extend table SAPSR3.D010TAB by 128 in tablespace PSAPSR3700
BR0976W Database message alert - level: ERROR, line: 202054, time: 2008-03-03 17.16.14, message:
ORA-1653: unable to extend table SAPSR3.D010TAB by 128 in tablespace PSAPSR3700
BR0976W Database message alert - level: ERROR, line: 202055, time: 2008-03-03 17.16.14, message:
I was quite surprised because the tablespace PSAPSR3700 wasn't saturated (20% free), nevertheless
I have added a new datafile to the tablespace, but still I'm getting the same error message.
Tablespace Size (kb) Free (kb) Used (%) Tab/ind Extents AutoExt (kb) Used (%) Status Backup
PSAPSR3700 105.861.120 28.370.176 73 861 11.051 Off 73 ONLINE NOT ACTIVE
I have 28 Gb of free space in tablespace PSAPSR3700 and the system can not extend a 2Gb table ???
How is it possible ?
Owner Object Type Tablespace KBytes Blocks Extents MaxExtents Next (K)
SAPSR3 D010TAB TABLE PSAPSR3700 2.031.616 253.952 199 1- 0
I've refreshed the Oracle statistics but it didcn't help either.
Thank you for your help.
Best Regards.
Hello Indus,
have you seen the date of the alert?
>ORA-1653: unable to extend table SAPSR3.D010TAB by 128 in tablespace PSAPSR3700
>BR0976W Database message alert - level: ERROR, line: 202054, time: 2008-03-03 17.16.14, message:
>ORA-1653: unable to extend table SAPSR3.D010TAB by 128 in tablespace PSAPSR3700
>BR0976W Database message alert - level: ERROR, line: 202055, time: 2008-03-03 17.16.14, message
I think that there was a problem on 03.03.2008 and an admin has extended the tablespace.
Regards
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Indus,
This might be due to NEXT EXTENT size being higher than the amount of contiguous space available in your tablespace.
A tablespace reorg should fix this.
Regards,
Siddhesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.