- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- backup script wierdness after database migration
Operating System - HP-UX
1752806
Members
5810
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2003 09:44 AM
тАО04-09-2003 09:44 AM
backup script wierdness after database migration
I recently migrated our production database from 7.3.4 to 8i. We are still running Oracle Applications 10.7SC. We have always done a cold backup (using omniback) on sunday mornings. A script (dbappshut.sh) is called and stops concurrent managers then shuts down the database. After the backup completes, another script (dbappstart.sh) starts everything up again. The logs in omniback show the scripts as running successfully. The problem is that concurrent jobs error out after the restart, giving REP-0001 errors - which according to Metalink are caused by not starting the managers as the APPLMGR user. the scripts with managers ARE run as the APPLMGE user - which I verified since each script does an (id) and (env) command to a log file. When I bounce the managers, the errors go away. It seems that there is an environment variable that was set correctly when we had the 7.3.4 database, but is now not correct in the server partitioned environment (I am wondering about ORA_NLS33??). Has anyone else had problems in this scenario? Any suggestions?
Thanks
Thanks
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2003 09:46 AM
тАО04-09-2003 09:46 AM
Re: backup script wierdness after database migration
One - more item - I have attached a copy of the script outputs (the id and env outputs).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2003 11:11 PM
тАО04-09-2003 11:11 PM
Re: backup script wierdness after database migration
Hi,
It could be related to an environment variable as you said.
I have checked your attachment and the variable ORA_NLS33=/u01/oracle/8.1.7/ocommon/nls/admin/datat seems to be set correctly. The only difference is in oracle 7.3.4 you would have ORA_NLS32 = $ORACLE_HOME/ocommon/nls/admin/data and oracle 8 you would have ORA_NLS33 = $ORACLE_HOME/ocommon/nls/admin/data.
I was thinking of another variable LD_LIBRARY_PATH.Can you set this to LD_LIBRARY_PATH to include $ORACLE_HOME/lib and see if it fixes. Because if this variable is not defined, then the dynamic linker cannot locate any shared libraries and Oracle Application Object Library 10.7 will give errors when running any concurrent request.
It could be related to an environment variable as you said.
I have checked your attachment and the variable ORA_NLS33=/u01/oracle/8.1.7/ocommon/nls/admin/datat seems to be set correctly. The only difference is in oracle 7.3.4 you would have ORA_NLS32 = $ORACLE_HOME/ocommon/nls/admin/data and oracle 8 you would have ORA_NLS33 = $ORACLE_HOME/ocommon/nls/admin/data.
I was thinking of another variable LD_LIBRARY_PATH.Can you set this to LD_LIBRARY_PATH to include $ORACLE_HOME/lib and see if it fixes. Because if this variable is not defined, then the dynamic linker cannot locate any shared libraries and Oracle Application Object Library 10.7 will give errors when running any concurrent request.
Never give up, Keep Trying
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-15-2003 11:56 AM
тАО04-15-2003 11:56 AM
Re: backup script wierdness after database migration
I ended up setting the ORA_NLS33 parameter in the script that starts the concurrent managers. This works - though several other things broke (due to NLS_LANG not being also set). Thnks
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP