cancel
Showing results for 
Search instead for 
Did you mean: 

Brtools online Backup Error

Former Member
0 Kudos

Hi Team,

Unfortunately our Development server was crashed. we have restored the latest online + Archive backup and

started SAP Services. SAP is up and Running fine. We have tried to start DB online backup through BRtools

and getting the below error.

===================================================================================

BR0484I BRBACKUP log file: /oracle/GD1/sapbackup/bekufsws.and

BR0334E Status of database file /oracle/GD1/112_64/dbs/MISSING00039 is RECOVER

BR0274W File '/oracle/GD1/112_64/dbs/MISSING00039' not found

BR0334E Status of database file /oracle/GD1/112_64/dbs/MISSING00040 is RECOVER

BR0334E Status of database file /oracle/GD1/112_64/dbs/MISSING00041 is RECOVER

BR0274W File '/oracle/GD1/112_64/dbs/MISSING00041' not found

BR0334E Status of database file /oracle/GD1/112_64/dbs/MISSING00042 is RECOVER

BR0274W File '/oracle/GD1/112_64/dbs/MISSING00042' not found

BR0334E Status of database file /oracle/GD1/112_64/dbs/MISSING00047 is RECOVER

BR0274W File '/oracle/GD1/112_64/dbs/MISSING00047' not found

BR0334E Status of database file /oracle/GD1/112_64/dbs/MISSING00048 is RECOVER

BR0274W File '/oracle/GD1/112_64/dbs/MISSING00048' not found

BR0314E Collection of information on database files failed

BR0056I End of database backup: bekufsws.and 2013-03-19 21.17.02

BR0280I BRBACKUP time stamp: 2013-03-19 21.17.02

BR0054I BRBACKUP terminated with errors

===================================================================================

We have analyed the issue at DB Level and found 6 datafile is not showing.(select * from v$backup;)

 

SQL> select FILE#,NAME from v$datafile where STATUS='RECOVER';

     FILE#,NAME

--------------------------------------------------------------------------------

        39 /oracle/GD1/112_64/dbs/MISSING00039

        40 /oracle/GD1/112_64/dbs/MISSING00040

        41 /oracle/GD1/112_64/dbs/MISSING00041

         42 /oracle/GD1/112_64/dbs/MISSING00042

         47 /oracle/GD1/112_64/dbs/MISSING00047

        48 /oracle/GD1/112_64/dbs/MISSING00048

6 rows selected.

SQL>

Kindly suggest us to resolve this issue

Regards

Senthil

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Senthil,

I  have faced this issue before. You are getting this error because you have created the control file in a wrong way.

You have to create a valid control file to fix this issue. Please follow the below steps.

1.stop SAP system and DB as well.

2.if you have any valid control file in your backup , place it in the place where you have specified the location of the control file in your  initGD1.ora which is available in /oracle/GD1/112_64/dbs folder.

3. login as orasid

4.sqlplus "/as sysdba"

5.create spfile from pfile.

6.startup

This should hopefully fix the issue.

Thanks and Regards,

Vimal

former_member206552
Active Contributor
0 Kudos

Vimal,

suppose he can find the valid controlfile in the alert_SID.log

regards

marius

Former Member
0 Kudos

In that case, I would suggest you to create a new control file again and check.

Iam 99% confident that this issue COULD BE due to incorrect control file creation.

Former Member
0 Kudos

This will create spfile, not control file

Former Member
0 Kudos

Hi,

   After setting the correct path of control files, we need to create spfile from pfile and start the DB.

Thanks and  Regards,

Vimal

former_member188883
Active Contributor
0 Kudos

Hi Michal,

You may use

Alter database backup controlfile to trace;

To generate a controfile.

Regards,

Deepak Kori

Former Member
0 Kudos

Hi sir,

i have tried all these steps and again created a control file but its not working.

Please help me ASAP

Thanks,

Ashish

Answers (3)

Answers (3)

Former Member
0 Kudos

This message was moderated.

Former Member
0 Kudos

Hi Senthil and Michal,

I just experienced a similar issue after restoring the database for a system copy.

With brtools I had a look at the datafiles and realized that they should belong to a tablespace that no longer existed. (Java-stack.)
Since I knew that there was no needed content in the files I dropped the table-space in force-mode and afterwards the database was in proper state.

Maybe you are lucky and have a similar situation.

Good luck,

Henning

former_member188883
Active Contributor
0 Kudos

Hi Senthil,

Could you find which tablespace these files belong to ?

Regards,

Deepak Kori