Solution is, previously by mistakenly we triggered the incremental offline backup due to this we got the subjected issue.
Now we corrected.(incremental online backup).
Thanks for your valuable inputs and time.
Regards,
Vijaya
Hi Experts,
Small correction in my request...we are triggering Incremental Online Backup.
Regards,
Vijaya
Hi Prakash,
The user which are using to access the database have all the permissions for accessing the services.
and when the load is high(running morning batch jobs and DB backup both are at same time) on database at that time the DB is restarting.
Regards,
Vijaya
Hi Prakash,
I will check and let you know.
Regards,
Vijaya
Hi Vijaya,
Since your SAP system running on windows operating system, please check and let us know which your user you have used to start the oracle instance check in (services.MSC)
You have to ensure that the Oracle environment (ORACLE_HOME, ORACLE_SID, ORACLE_BASE) is identical to the user which you used to start , If ORACLE_HOME differs, you will get an ORA-01033: ORACLE initialization or shutdown message even the instance is up and running.
Regards
JP
Hi Vijaya,
Since your SAP system running on your windows operating system, please check and let us know which your user you have used to start the oracle instance check in (services.MSC)
You have to ensure that the Oracle environment (ORACLE_HOME, ORACLE_SID, ORACLE_BASE) is identical to the user which you used to start , If ORACLE_HOME differs, you will get an ORA-01033: ORACLE initialization or shutdown in progress error when starting SAP.
Regards
JP
Hi Jayaprakash,
Our BR*Tools version is 740 and the patch level is 34.
Regards,
Vijaya
Hi Vijaya,
Please let us know your BR*tools version and patch level, for Ehp7 the version is 740... if its less than 7.40 Patch 1,
we can upgrade and see the results. also refer the SAP note 1838852 - Corrections in BR*Tools 7.20 Patch 31 / 7.40 Patch 1
Regards
JP
Hi Jayaprakash,
Thanks for your input.
We are not using stand by DB.
Thanks & Regards,
Vijaya
Hi Manu,
Yes, it is a remote connection and we triggered Incremental Offline Backup.
Thanks & Regards,
Vijaya
is it a remote database connection? Did u trigger an offline backup
Hi Vijaya,
If the oracle alerts comes during backup of archive files then check the BRARCHIVE must be called on the standby page with the "-m" option
ORA-01033 is related to the starting up or shutting down of Oracle. There are several possible causes and fixes to the problem.
The Problem
The ORA-01033 error message is as follows:
ORACLE initialization or shutdown in progress
The most likely cause is that an attempt was made to log on while Oracle is either starting up or shutting down. Otherwise, you may be facing one of the following problems:
- The database was not mounted properly.
- There is a problem with the database files—They may have been moved or are corrupt (CTL, DBF, ORA).
- There is a problem with the database service.
The Solution
Check to see if the database is in the process of starting up or shutting down. Wait a few minutes for Oracle to finish, then try the operation again. If this is unsuccessful, restart the system and restart the database service.
Another possibility for the error is that your operating system holds RAM regions left over which Oracle takes as an instance that is already running. If this is the case, you must kill all Oracle processes associated with the ORACLE_SID. Identify all RAM memory segments, then release the RAM memory.
If the database was not mounted properly, you must mount and restart the database. Do this by querying “alter the database mount” and “alter database open”.
If there is a problem with the database files, the files may have been changed or moved to a different location. Locate and recover the files if this is the case.
Lastly, if there is a problem with the database service, restart the database service in services. msc.
In addition, if you are getting ORA-19809 in addition to ORA-01033, the solution may lie within fixing ORA-19809, which occurs when the limit is exceeded for recovery files.
A last resort may be deleting the service and database, then recreating it. If you choose to try this method, make sure your data is backed up. In service.msc, stop the service and delete the service. Then recreate the database.
Looking Forward
To avoid getting ORA-01033, make sure Oracle is not in the process of starting up or shutting down. Make sure the database is mounted properly and there are no problems with the database service or files. A simple solution to many problems faced in Oracle requires shutting down and restarting. This may easily resolve some Oracle errors. If you continue seeing ORA-01033, contact your database administrator for assistance. You may consider consulting a licensed Oracle professional.