26 Replies Latest reply: Feb 20, 2012 11:09 AM by Marc Pont RSS

DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full

Marc Pont
Currently Being Moderated

Dear SAP gurus,

 

This is an a SAP ERP60 EHP3 system with Oracle we  are in the process of patching it. First, We have download all sw components patches (EHP3 SPS6) we patched java stack and then the sw components -SAP_ABA and SAP_BASIS from SP17 to SP22.

We ran SGEN for SAP_ABA and SAP_BASIS and it is when the issues start coming out.

 

"2.043 generation error(s): Tablespace is possibly full (with load tables)"

 

Then we tried to access any SAP Transaction related to ORacle:

"DBIF_REPO_SQL_ERROR".

From work process logs:

 

C Wed Feb 15 11:02:26 2012

C OCIStmtExecute() failed with -1=OCI_ERROR

C SQL error 600:

C *** ERROR => Error 600 in stmt_execute() from oci_execute_stmt(),

orpc=119

[dbsloci.c 12981]

C *** ERROR => ORA-600 occurred when executing SQL stmt (parse error

offset=0)

[dbsloci.c 12983]

C

sc_p=0x5901b30,no=182,idc_p=0x5917a88,con=0,astyle='font-family:courier'

ct=1,slen=67,smax=256,#vars=

2,stmt=0x5dcaa30,table=D010INC

C INSERT INTO "D010INC" ( "MASTER" , "INCLUDE" ) VALUES ( :A0 , :A1 );

C

sc_p=0x5901b30,no=182,idc_p=0x5917a88,con=0,astyle='font-family:courier'

ct=1,slen=67,smax=256,#vars=

2,stmt=0x5dcaa30,table=D010INC

C Dumping DBSL stmt. cache:

C prep=0,lit=0,nsql=0,lobret=0,xop=1,dbcnt=119,upsh=

(nil),stmtp=0x5bcc0f8,rtc=0

C IN :

cols=2,rmax=387,xcnt=232,rpc=0,rowi=232,rtot=232,upto=4294967295,rsize=16

0,vmax=32,bound=1,iobuf_p=0x5a2a7b0,vda_p=0x5db8470

C lobs=0,lmax=0,lpcnt=0,larr=(nil),lcurr_p=(nil),rret=0

C INSERT INTO "D010INC" ( "MASTER" , "INCLUDE" ) VALUES ( :A0 , :A1 );

B ***LOG BYL=> DBQ action required because of database error

 

[dbsh#3 @ 1104] [dbsh 1104 ]

B SQL code: 600, SQL text: ORA-00600: internal error code, arguments:

[4553], [2], [0], [], [], [], [], []

B ***LOG BY4=> sql error 600 performing CLC on table D010INC

[dbrepo#5 @ 6034] [dbrepo 6034 ]

B ***LOG BY0=> ORA-00600: internal error code, arguments: [4553], [2],

[0], [], [], [], [], [] [dbrepo#5 @ 6034] [dbrepo 6034 ]

B DBREPO: new rc return for insert_inc_difference

A TH VERBOSE LEVEL FULL

 

We tried to extend the tablespace PSAPSR700 (which is related to table

D010INC) but we are still getting dumps like "DBIF_REPO_SQL_ERROR".

 

Can you please guide us how to proceed?This query is very urgent since we

prefer that our developers do not work until we resolve the issue.

 

Thanks in advance, Marc

  • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
    Vijaylakshmi Horakeri
    Currently Being Moderated

    Hi Marc,

     

    Can you try to run DB verify from DB13 and check for issues.

    Also check the oracle alert log file for more error info.

     

    Thanks & Regards,

    Vijaya

    • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
      Marc Pont
      Currently Being Moderated

      Hi Vijaya,

       

      No access to DB13 either...

      Form brtools-->DB system check

       

      BR0280I BRCONNECT time stamp: 2012-02-16 09.43.13

      BR0813I Schema owners found in database SHD:

      CLAUDIO, DBSNMP, DIP, MGMT_VIEW, OPS$ORASHD, OPS$SAPSERVICESHD, OPS$SHDADM, OPS$SR3ADM, ORACLE_OCM, OUTLN,

      SAPSR3*, SAPSR3DB%, SYS, SYSMAN, SYSTEM, TSMSYS

       

      BR0280I BRCONNECT time stamp: 2012-02-16 09.43.30

      BR0814I Number of tables in schema of owner SAPSR3: 72320

      BR0836I Number of info cube tables found for owner SAPSR3: 49

      BR0814I Number of tables in schema of owner SAPSR3DB: 643

      BR0814I Number of tables/partitions in schema of owner SYS: 625/153

      BR0814I Number of tables/partitions in schema of owner SYSTEM: 134/27

       

      BR0280I BRCONNECT time stamp: 2012-02-16 09.43.38

      BR0815I Number of indexes in schema of owner SAPSR3: 86423

      BR0815I Number of indexes in schema of owner SAPSR3DB: 961

      BR0815I Number of indexes/partitions in schema of owner SYS: 678/161

      BR0815I Number of indexes/partitions in schema of owner SYSTEM: 175/32

       

      BR0280I BRCONNECT time stamp: 2012-02-16 09.44.21

      BR0816I Number of segments in schema of owner DBSNMP: 25

      BR0816I Number of segments in schema of owner OPS$SHDADM: 1

      BR0816I Number of segments in schema of owner OUTLN: 9

      BR0816I Number of segments/LOBs in schema of owner SAPSR3: 163127/2192

      BR0816I Number of segments/LOBs in schema of owner SAPSR3DB: 2124/260

      BR0816I Number of segments/LOBs in schema of owner SYS: 1759/87

      BR0816I Number of segments in schema of owner SYSMAN: 765

      BR0816I Number of segments/LOBs in schema of owner SYSTEM: 353/22

      BR0816I Number of segments in schema of owner TSMSYS: 4

       

      BR0280I BRCONNECT time stamp: 2012-02-16 09.44.21

      BR0961I Number of conditions found in DBCHECKORA: 118

       

      BR0280I BRCONNECT time stamp: 2012-02-16 09.44.21

      BR0818I Number of tables found in DBDIFF for owner SAPSR3: 2

       

      BR0280I BRCONNECT time stamp: 2012-02-16 09.44.21

      BR0818I Number of tables found in DBSTATC for owner SAPSR3: 390

       

      BR0280I BRCONNECT time stamp: 2012-02-16 09.44.21

      BR0807I Name of database instance: SHD

      BR0808I BRCONNECT action ID: cehxcklj

      BR0809I BRCONNECT function ID: chk

      BR0810I BRCONNECT function: check

      BR0951I Number of active/inactive check conditions for database administration: 22/1

      BR0952I Number of active/inactive check conditions for database operations: 7/3

      BR0953I Number of active/inactive check conditions for database messages: 58/0

      BR0954I Number of active/inactive check conditions for database profile: 27/0

       

      Alert_SID.log only have the error I posted earlier...

       

      Thu Feb 16 08:58:33 2012

      Errors in file /oracle/SHD/saptrace/usertrace/shd_ora_31639.trc:

      ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

      Thu Feb 16 08:58:39 2012

      Doing block recovery for file 2 block 167667

      Block recovery from logseq 19229, block 81983 to scn 1338733087

       

      thanks, Marc

      • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
        Marc Pont
        Currently Being Moderated

        This might be interesting too...

         

        BR0280I BRCONNECT time stamp: 2012-02-16 09.53.38

        BR0974I Checking database messages in /oracle/SHD/saptrace/background/alert_SHD.log ...

        BR0976W Database message alert - level: ERROR, line: 447865, time: 2012-02-16 08.54.43, message:

        ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

        BR0976W Database message alert - level: ERROR, line: 447891, time: 2012-02-16 08.54.52, message:

        ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

        BR0976W Database message alert - level: ERROR, line: 447916, time: 2012-02-16 08.55.07, message:

        ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

        BR0976W Database message alert - level: ERROR, line: 447941, time: 2012-02-16 08.55.15, message:

        ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

        BR0976W Database message alert - level: ERROR, line: 447966, time: 2012-02-16 08.58.33, message:

        ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

        BR0976W Database message alert - level: ERROR, line: 447991, time: 2012-02-16 08.58.40, message:

        ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

        BR0976W Database message alert - level: ERROR, line: 448024, time: 2012-02-16 09.16.22, message:

        ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

        BR0976W Database message alert - level: ERROR, line: 448053, time: 2012-02-16 09.16.28, message:

        ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

        BR0976W Database message alert - level: ERROR, line: 448082, time: 2012-02-16 09.43.42, message:

        ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

        BR0976W Database message alert - level: ERROR, line: 448108, time: 2012-02-16 09.43.49, message:

        ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

  • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
    Venkata Pagolu
    Currently Being Moderated

    Hi,

     

    Please perform DBcheck once and let me know the result.

     

    Regards,

    Venkata S Pagolu

    • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
      Marc Pont
      Currently Being Moderated

      Hi Venkata,

       

      Please have a look at the results above.

      Let me know if you need anything else.

       

      thanks, Marc

      • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
        Venkata Pagolu
        Currently Being Moderated

        Hi,

         

        If you have metalink access, please go through below link for solution.

         

        ORA-600 Lookup Tool

        [https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=153788.1]

         

        Regards,

        Venkata S Pagolu

        • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
          Marc Pont
          Currently Being Moderated

          Sorry Venkata,

           

          I cannot access to it, can you paste the solution?

           

          Thanks, Marc

          • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
            Venkatesh Pydi
            Currently Being Moderated

            Hi Marc,

             

            There seems to be corruption in the datafile 2.

            Could you please port the more lines from alert log and trace files.

             

            Meanwhile you can run rman validation.

             

            rman nocatalog

            connect target /

            backup check logical validate (datafile 2) ;

             

            For running this while the database is online and no need to have the rman configured.

             

            Let us know the results.

             

            Br,

            Venky

            • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
              Marc Pont
              Currently Being Moderated

              Thanks for your reply Venky,

               

               

              RMAN> connect target /

               

              connected to target database: SHD (DBID=1683093070)

              using target database control file instead of recovery catalog

               

              RMAN> backup check logical validate (datafile 2);

               

              Starting backup at 16-FEB-12

              allocated channel: ORA_DISK_1

              channel ORA_DISK_1: sid=193 devtype=DISK

              channel ORA_DISK_1: starting full datafile backupset

              channel ORA_DISK_1: specifying datafile(s) in backupset

              RMAN-00571: ===========================================================

              RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

              RMAN-00571: ===========================================================

              RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/16/2012 12:22:36

              ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

               

               

              alert_SID.log

               

              Thu Feb 16 09:43:42 2012

              Errors in file /oracle/SHD/saptrace/usertrace/shd_ora_3380.trc:

              ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

              Thu Feb 16 09:43:47 2012

              Doing block recovery for file 2 block 3455

              Block recovery from logseq 19230, block 22155 to scn 1338742588

              Thu Feb 16 09:43:47 2012

              Recovery of Online Redo Log: Thread 1 Group 2 Seq 19230 Reading mem 0

                Mem# 0: /oracle/SHD/origlogB/log_g12m1.dbf

                Mem# 1: /oracle/SHD/mirrlogB/log_g12m2.dbf

              Block recovery completed at rba 19230.22329.16, scn 0.1338742589

              Doing block recovery for file 2 block 297161

              Block recovery from logseq 19230, block 12545 to scn 1338742588

              Thu Feb 16 09:43:47 2012

              Recovery of Online Redo Log: Thread 1 Group 2 Seq 19230 Reading mem 0

                Mem# 0: /oracle/SHD/origlogB/log_g12m1.dbf

                Mem# 1: /oracle/SHD/mirrlogB/log_g12m2.dbf

              Block recovery completed at rba 19230.22329.16, scn 0.1338742589

              Doing block recovery for file 35 block 352889

              Block recovery from logseq 19230, block 22155 to scn 1338742590

              Thu Feb 16 09:43:48 2012

              Recovery of Online Redo Log: Thread 1 Group 2 Seq 19230 Reading mem 0

                Mem# 0: /oracle/SHD/origlogB/log_g12m1.dbf

                Mem# 1: /oracle/SHD/mirrlogB/log_g12m2.dbf

              Block recovery stopped at EOT rba 19230.22329.16

              Block recovery completed at rba 19230.22329.16, scn 0.1338742589

              Thu Feb 16 09:43:49 2012

              Errors in file /oracle/SHD/saptrace/usertrace/shd_ora_30410.trc:

              ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

              Thu Feb 16 09:43:54 2012

               

               

              dev_server0

               

               

              Wed Feb 15 10:55:06 2012

              GENER request remote generation: CL_SRT_WSP_HELPER_METHODS=====CP.

              A

              A Wed Feb 15 10:55:19 2012

              GENER request remote generation: RSDSOSCCM.

              A

              A Wed Feb 15 10:55:23 2012

              GENER starting inline generation: RSDSOSCCM (reason: compile error during remote generation).

              C

              C Wed Feb 15 10:55:26 2012

              C     OCIStmtExecute() failed with -1=OCI_ERROR

              C     SQL error 600:

              C  *** ERROR => Error 600 in stmt_execute() from oci_execute_stmt(), orpc=9

              [dbsloci.c    12981]

              C  *** ERROR => ORA-600 occurred when executing SQL stmt (parse error offset=0)

              [dbsloci.c    12983]

              C  sc_p=0x58fd3f0,no=62,idc_p=0x5916100,con=0,act=1,slen=67,smax=256,#vars=2,stmt=0x5cecfb0,table=D010INC

              C  INSERT INTO "D010INC" ( "MASTER" , "INCLUDE" ) VALUES ( :A0 , :A1 );

              C  sc_p=0x58fd3f0,no=62,idc_p=0x5916100,con=0,act=1,slen=67,smax=256,#vars=2,stmt=0x5cecfb0,table=D010INC

              C  Dumping DBSL stmt. cache:

              C  prep=0,lit=0,nsql=0,lobret=0,xop=1,dbcnt=9,upsh=(nil),stmtp=0x5cedc58,rtc=0

              C  IN : cols=2,rmax=387,xcnt=9,rpc=0,rowi=9,rtot=9,upto=4294967295,rsize=160,vmax=32,bound=1,iobuf_p=0x5da5400,vda_p=0x5cee310

              C       lobs=0,lmax=0,lpcnt=0,larr=(nil),lcurr_p=(nil),rret=0

              C  INSERT INTO "D010INC" ( "MASTER" , "INCLUDE" ) VALUES ( :A0 , :A1 );

              B  ***LOG BYL=> DBQ action required because of database error            [dbsh#3 @ 1104] [dbsh    1104 ]

              B  SQL code: 600, SQL text: ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []

              B  ***LOG BY4=> sql error 600    performing CLC on table D010INC    [dbrepo#5 @ 6034] [dbrepo  6034 ]

              B  ***LOG BY0=> ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], [] [dbrepo#5 @ 6034] [dbrepo  6034 ]

              B  DBREPO: new rc return for insert_inc_difference

              A  TH VERBOSE LEVEL FULL

              A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

              A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

              A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

              A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

              A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.

              A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.

              A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

               

               

              Regards, Marc

              • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                Venkatesh Pydi
                Currently Being Moderated

                Hi Marc,

                 

                Give us the output of the following

                select * from v$datafile where status like 'REC%';

                 

                What stage is the system at the moment?

                Can't we bring the system to ARCHIVE LOG mode and rman?

                It is always recommended to run the db in archive log mode.

                 

                Findout the which datafile is with number 2.

                 

                You would also be interested to run dbverify on the datafile if there are any datafiles in recover mode.

                 

                Br,

                Venky

                • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                  Marc Pont
                  Currently Being Moderated

                  Thanks Venky,

                   

                  >Give us the output of the following

                  >select * from v$datafile where status like 'REC%';

                   

                  SQL> select * from v$datafile where status like 'REC%';

                   

                  no rows selected

                   

                  >What stage is the system at the moment?

                  The system is up and running. But I dont have access to any of the transactions access to Oracle like DBACOCKPIT, DB13, DB02, etc...

                  >Can't we bring the system to ARCHIVE LOG mode and rman?

                  >It is always recommended to run the db in archive log mode.

                  I set archive log mode and find below the output of rman...

                   

                  RMAN> backup check logical validate (datafile 2) ;

                   

                  Starting backup at 16-FEB-12

                  allocated channel: ORA_DISK_1

                  channel ORA_DISK_1: sid=209 devtype=DISK

                  channel ORA_DISK_1: starting full datafile backupset

                  channel ORA_DISK_1: specifying datafile(s) in backupset

                  input datafile fno=00002 name=/oracle/SHD/sapdata3/undo_1/undo.data1

                  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15

                  Finished backup at 16-FEB-12

                   

                  I will provide the dbverify output later.

                   

                  Regards, Marc

                  • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                    Venkatesh Pydi
                    Currently Being Moderated

                    Hi Marc,

                     

                    Did you reboot the system after setting archive log mode on? If yes, Do you still see the same errors?

                    Please increase UNDO tablespace.

                    What is the current database size? If the DB size is not very high, I would suggest to run a full rman backup validation.

                     

                    Br,

                    Venky

                    • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                      Marc Pont
                      Currently Being Moderated

                      Thanks Venky,

                       

                      >Did you reboot the system after setting archive log mode on? If yes, Do you still see the same errors?

                      I forced archivelog with Force instance shutdown (force) . [yes]...  plus I restarted the system. But I sitll have the same issues...

                       

                      >Please increase UNDO tablespace

                       

                      List of database tablespaces

                       

                      Pos.  Tablespace     Type  Status    ExtMan.  SegMan.  Backup  Files/AuExt.

                            Total[KB]   Used[%]    Free[KB]  MaxSize[KB]  ExtSize[KB]  FreeExt.    Largest[KB]

                       

                        1 - PSAPSR3        DATA  ONLINE    LOCAL    AUTO      NO        20/20

                            64040960     98.11     1208320    102400000     38359040       118     2211840:2150400:2109440:2048000:2048000+

                        2 - PSAPSR3700     DATA  ONLINE    LOCAL    AUTO      NO        17/17

                            50237440     93.99     3021056     87040000     36802560        18     2969536:2314240:2293760:2273280:2232320

                        3 - PSAPSR3DB      DATA  ONLINE    LOCAL    AUTO      NO         3/3

                             5120000     73.23     1370624     30720000     25600000         3     9216000:8192000:8192000+:710592:659392

                        4 - PSAPSR3USR     DATA  ONLINE    LOCAL    AUTO      NO         1/1

                               20480     40.31       12224     10240000     10219520         1    10219520+:12224:0:0:0

                        5 - PSAPTEMP       TEMP  ONLINE    LOCAL    MANUAL    NO         1/1

                             2048000      0.00     2048000     10240000      8192000         0     8192000+:0:0:0:0

                        6 - PSAPUNDO       UNDO  ONLINE    LOCAL    MANUAL    NO         1/1

                             7823360      0.00     7823296     10240000      2416640       410     3760064:2416640+:1435648:675840:277504

                        7 - SYSAUX         DATA  ONLINE    LOCAL    AUTO      NO         1/1

                              593920     96.90       18432     10240000      9646080        30     9646080+:11200:832:768:640

                        8 - SYSTEM         DATA  ONLINE    LOCAL    MANUAL    NO         1/1

                              962560     98.66       12864     10240000      9277440         3     9277440+:12224:576:64:0

                       

                      Undo tablespace is quite empty so I dont think this is the issue.

                       

                      >What is the current database size? If the DB size is not very high, I would suggest to run a full rman backup validation.

                      Oracle is 200GB, I will pass you the dbverify once it is done.

                       

                      Any ideas?

                      Regards, Mac

                      • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                        Venkatesh Pydi
                        Currently Being Moderated

                        Hi Marc,

                         

                        Remember that RMAN validate is more powerful and accurate than DBVERIFY.

                        DBVERY will run for longer time than RMAN.

                        Hence, I would suggest you to stick to RMAN validate

                         

                        Br,

                        Venky

                      • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                        Marc Pont
                        Currently Being Moderated

                        6 - Verification of database backup

                         

                        BR0420I Files will be restored from directory: /mnt/backup/oracle/SHD/behwgtlm

                        BR0147I Verify option set - verification of backup only, no restore

                         

                         

                        BR0280I BRRESTORE time stamp: 2012-02-16 13.19.40

                        BR0418I 48 of 49 files restored - 123800.346 of 123814.080 MB done

                        BR0204I Percentage done: 99.99%, estimated end time: 13:19

                        BR0001I **************************************************

                         

                        BR0353I Verifying backup of /oracle/SHD/origlogA/cntrl/cntrlSHD.dbf

                        BR0355I from /mnt/backup/oracle/SHD/behwgtlm/cntrlSHD.dbf ...

                         

                        BR0362I Verification of backup of /oracle/SHD/origlogA/cntrl/cntrlSHD.dbf successful

                         

                        BR0280I BRRESTORE time stamp: 2012-02-16 13.19.40

                        BR0418I 49 of 49 files restored - 123814.080 of 123814.080 MB done

                        BR0204I Percentage done: 100.00%, estimated end time: 13:19

                        BR0001I **************************************************

                         

                        BR0406I End of file restore: rehxdbya.rsb 2012-02-16 13.19.40

                        BR0280I BRRESTORE time stamp: 2012-02-16 13.19.40

                        BR0402I BRRESTORE completed successfully

                         

                        ###############################################################################

                         

                        BR0292I Execution of BRRESTORE finished with return code 0

                         

                         

                        all successful...

                         

                        Regards, MArc

                        • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                          Venkatesh Pydi
                          Currently Being Moderated

                          Hi Marc,

                           

                          Could you please run rman validate as well. Then, we can ensure that db is without corruption.

                          DBVerify sometimes will not show the error if it is logical.

                           

                          Br,

                          Venky

                          • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                            Marc Pont
                            Currently Being Moderated

                            Hi Venki,

                             

                            RMAN> backup validate database;

                             

                            Starting backup at 16-FEB-12

                            allocated channel: ORA_DISK_1

                            channel ORA_DISK_1: sid=189 devtype=DISK

                            channel ORA_DISK_1: starting full datafile backupset

                            channel ORA_DISK_1: specifying datafile(s) in backupset

                            input datafile fno=00002 name=/oracle/SHD/sapdata3/undo_1/undo.data1

                            input datafile fno=00021 name=/oracle/SHD/sapdata4/sr3_18/sr3.data18

                            input datafile fno=00023 name=/oracle/SHD/sapdata4/sr3_20/sr3.data20

                            input datafile fno=00005 name=/oracle/SHD/sapdata1/sr3_2/sr3.data2

                            input datafile fno=00022 name=/oracle/SHD/sapdata4/sr3_19/sr3.data19

                            input datafile fno=00004 name=/oracle/SHD/sapdata1/sr3_1/sr3.data1

                            input datafile fno=00009 name=/oracle/SHD/sapdata2/sr3_6/sr3.data6

                            input datafile fno=00020 name=/oracle/SHD/sapdata4/sr3_17/sr3.data17

                            input datafile fno=00006 name=/oracle/SHD/sapdata1/sr3_3/sr3.data3

                            input datafile fno=00018 name=/oracle/SHD/sapdata3/sr3_15/sr3.data15

                            input datafile fno=00007 name=/oracle/SHD/sapdata1/sr3_4/sr3.data4

                            input datafile fno=00019 name=/oracle/SHD/sapdata4/sr3_16/sr3.data16

                            input datafile fno=00008 name=/oracle/SHD/sapdata1/sr3_5/sr3.data5

                            input datafile fno=00011 name=/oracle/SHD/sapdata2/sr3_8/sr3.data8

                            input datafile fno=00037 name=/oracle/SHD/sapdata4/sr3700_14/sr3700.data14

                            input datafile fno=00038 name=/oracle/SHD/sapdata4/sr3700_15/sr3700.data15

                            input datafile fno=00012 name=/oracle/SHD/sapdata2/sr3_9/sr3.data9

                            input datafile fno=00010 name=/oracle/SHD/sapdata2/sr3_7/sr3.data7

                            input datafile fno=00015 name=/oracle/SHD/sapdata3/sr3_12/sr3.data12

                            input datafile fno=00016 name=/oracle/SHD/sapdata3/sr3_13/sr3.data13

                            input datafile fno=00017 name=/oracle/SHD/sapdata3/sr3_14/sr3.data14

                            input datafile fno=00025 name=/oracle/SHD/sapdata1/sr3700_2/sr3700.data2

                            input datafile fno=00030 name=/oracle/SHD/sapdata2/sr3700_7/sr3700.data7

                            input datafile fno=00031 name=/oracle/SHD/sapdata2/sr3700_8/sr3700.data8

                            input datafile fno=00013 name=/oracle/SHD/sapdata2/sr3_10/sr3.data10

                            input datafile fno=00024 name=/oracle/SHD/sapdata1/sr3700_1/sr3700.data1

                            input datafile fno=00026 name=/oracle/SHD/sapdata1/sr3700_3/sr3700.data3

                            input datafile fno=00027 name=/oracle/SHD/sapdata1/sr3700_4/sr3700.data4

                            input datafile fno=00039 name=/oracle/SHD/sapdata4/sr3700_16/sr3700.data16

                            input datafile fno=00044 name=/oracle/SHD/sapdata4/sr3700_17/sr3700.data17

                            input datafile fno=00029 name=/oracle/SHD/sapdata2/sr3700_6/sr3700.data6

                            input datafile fno=00014 name=/oracle/SHD/sapdata3/sr3_11/sr3.data11

                            input datafile fno=00028 name=/oracle/SHD/sapdata2/sr3700_5/sr3700.data5

                            input datafile fno=00032 name=/oracle/SHD/sapdata3/sr3700_9/sr3700.data9

                            input datafile fno=00035 name=/oracle/SHD/sapdata3/sr3700_12/sr3700.data12

                            input datafile fno=00034 name=/oracle/SHD/sapdata3/sr3700_11/sr3700.data11

                            input datafile fno=00036 name=/oracle/SHD/sapdata4/sr3700_13/sr3700.data13

                            input datafile fno=00033 name=/oracle/SHD/sapdata3/sr3700_10/sr3700.data10

                            input datafile fno=00041 name=/oracle/SHD/sapdata4/sr3db_1/sr3db.data1

                            input datafile fno=00042 name=/oracle/SHD/sapdata4/sr3db_2/sr3db.data2

                            input datafile fno=00043 name=/oracle/SHD/sapdata4/sr3db_3/sr3db.data3

                            input datafile fno=00001 name=/oracle/SHD/sapdata1/system_1/system.data1

                            input datafile fno=00003 name=/oracle/SHD/sapdata1/sysaux_1/sysaux.data1

                            input datafile fno=00040 name=/oracle/SHD/sapdata1/sr3usr_1/sr3usr.data1

                             

                            It only came out this during the last 10 min...

                            • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                              Venkatesh Pydi
                              Currently Being Moderated

                              Hi Marc,

                               

                              Hope you didn't get any error after rman validation.

                               

                              Could you please re-run SGEN and see

                               

                              Br,

                              Venky

                              • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                                Marc Pont
                                Currently Being Moderated

                                Hi Venky,

                                 

                                Unfortunately the error still persists (DBIF_REPO_SQL_ERROR). Any idea how to proceed?

                                 

                                Thanks, Marc

                                • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                                  Venkatesh Pydi
                                  Currently Being Moderated

                                  Hi Marc,

                                   

                                  Did you try updating the kernel?

                                  Especially R3trans, DBSL libraries.

                                   

                                  You will find dbsl.sar in the kernel area in the marketplace.

                                   

                                  And, try to rerun SGEN.

                                   

                                  Br,

                                  Venky

                                • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                                  Venkatesh Pydi
                                  Currently Being Moderated

                                  Hi Marc,

                                   

                                  Any luck on this issue?

                                   

                                  Br,

                                  Venky

                                  • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                                    Marc Pont
                                    Currently Being Moderated

                                    Hi Venky,

                                     

                                    Unfortunately, the issue still persists.

                                     

                                    Regards, Marc

                                    • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                                      Juan Reyes
                                      Currently Being Moderated

                                      Can you check and post errors on the DB logs alert_<sid>.log ?

                                       

                                      Regards

                                      Juan

                                      • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                                        Marc Pont
                                        Currently Being Moderated

                                        Hi Juan,

                                         

                                        >Can you check and post errors on the DB logs alert_<sid>.log ?

                                         

                                        BR0976W Database message alert - level: ERROR, line: 447865, time: 2012-02-16 08.54.43, message:

                                        ORA-00600: internal error code, arguments: 4553, [2], 0], [, ], [, ], [

                                        BR0976W Database message alert - level: ERROR, line: 447891, time: 2012-02-16 08.54.52, message:

                                        ORA-00600: internal error code, arguments: 4553, [2], 0], [, ], [, ], [

                                        BR0976W Database message alert - level: ERROR, line: 447916, time: 2012-02-16 08.55.07, message:

                                        ORA-00600: internal error code, arguments: 4553, [2], 0], [, ], [, ], [

                                        BR0976W Database message alert - level: ERROR, line: 447941, time: 2012-02-16 08.55.15, message:

                                        ORA-00600: internal error code, arguments: 4553, [2], 0], [, ], [, ], [

                                        BR0976W Database message alert - level: ERROR, line: 447966, time: 2012-02-16 08.58.33, message:

                                        ORA-00600: internal error code, arguments: 4553, [2], 0], [, ], [, ], [

                                        BR0976W Database message alert - level: ERROR, line: 447991, time: 2012-02-16 08.58.40, message:

                                        ORA-00600: internal error code, arguments: 4553, [2], 0], [, ], [, ], [

                                        BR0976W Database message alert - level: ERROR, line: 448024, time: 2012-02-16 09.16.22, message:

                                        ORA-00600: internal error code, arguments: 4553, [2], 0], [, ], [, ], [

                                        BR0976W Database message alert - level: ERROR, line: 448053, time: 2012-02-16 09.16.28, message:

                                        ORA-00600: internal error code, arguments: 4553, [2], 0], [, ], [, ], [

                                        BR0976W Database message alert - level: ERROR, line: 448082, time: 2012-02-16 09.43.42, message:

                                        ORA-00600: internal error code, arguments: 4553, [2], 0], [, ], [, ], [

                                        BR0976W Database message alert - level: ERROR, line: 448108, time: 2012-02-16 09.43.49, message:

                                        ORA-00600: internal error code, arguments: 4553, [2], 0], [, ], [, ], [

                                        ...

                                         

                                        Regards, Marc

                                        • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                                          Juan Reyes
                                          Currently Being Moderated

                                          lets make sure that all the blocks are out of the way

                                           

                                          We tried to extend the tablespace PSAPSR700

                                          Does the tablespaces have enough space now?... Also SGEN create a lot of redologs so you need to clean them and/or deactivate the archive log.

                                           

                                          Regards

                                          Juan

                                          • Re: DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full
                                            Marc Pont
                                            Currently Being Moderated

                                            Thanks Juan.

                                             

                                            >Does the tablespaces have enough space now?

                                            yes they have:

                                             

                                            Pos.  Tablespace     Type  Status    ExtMan.  SegMan.  Backup  Files/AuExt.

                                                  Total[KB]   Used[%]    Free[KB]  MaxSize[KB]  ExtSize[KB]  FreeExt.    Lar                                                                             gest[KB]

                                             

                                              1 - PSAPSR3        DATA  ONLINE    LOCAL    AUTO      NO        20/20

                                                  64040960     98.11     1208320    102400000     38359040       118     221                                                                             1840:2150400:2109440:2048000:2048000+

                                              2 - PSAPSR3700     DATA  ONLINE    LOCAL    AUTO      NO        17/17

                                                  50237440     93.99     3021056     87040000     36802560        18     296                                                                             9536:2314240:2293760:2273280:2232320

                                              3 - PSAPSR3DB      DATA  ONLINE    LOCAL    AUTO      NO         3/3

                                                   5120000     73.23     1370624     30720000     25600000         3     921                                                                             6000:8192000:8192000+:710592:659392

                                              4 - PSAPSR3USR     DATA  ONLINE    LOCAL    AUTO      NO         1/1

                                                     20480     40.31       12224     10240000     10219520         1    1021                                                                             9520+:12224:0:0:0

                                              5 - PSAPTEMP       TEMP  ONLINE    LOCAL    MANUAL    NO         1/1

                                                   2048000      0.00     2048000     10240000      8192000         0     819                                                                             2000+:0:0:0:0

                                              6 - PSAPUNDO       UNDO  ONLINE    LOCAL    MANUAL    NO         1/1

                                                   7823360      0.00     7823296     10240000      2416640       501     376                                                                             0064:2416640+:1435648:675840:277504

                                              7 - SYSAUX         DATA  ONLINE    LOCAL    AUTO      NO         1/1

                                                    593920     96.90       18432     10240000      9646080        44     964                                                                             6080+:10496:1024:1024:448

                                              8 - SYSTEM         DATA  ONLINE    LOCAL    MANUAL    NO         1/1

                                                    962560     98.66       12864     10240000      9277440         3     927                                                                             7440+:12224:576:64:0

                                             

                                            >Also SGEN create a lot of redologs so you need to clean them and/or deactivate the archive log

                                            It was set up "no archive log" during SGEN

                                             

                                            Regards, Marc

Actions