change Oracle SID for Veritas Back-up exec agent

Posted on 2006-05-16
Medium Priority
Last Modified: 2013-12-12
Hi there,

we run an Oracle database version 10g which we want to back-up with the (Veritas) Symantec back-up exec Oracle agent.

The Oracle database has an SID of 10 characters, the problem is that the back-up exec agent can only fit 8 characters for the database SIDthat we want to back-up.

Any suggestions on how to solve this problem? (change SID name, install patch for Symantec, create an Alias) Please include step by step instructions.

Thanks alot
Question by:geert_zaal
  • 4
  • 2
LVL 78

Expert Comment

by:slightwv (䄆 Netminder)
ID: 16701697
First:  I haven't messed with Veritas for a long time so I my be way off base but...

I'm thinking that Veritas uses the tnsnames.ora to get it's info.  Try creating an alias with a shorter name and give that to Veritas.

If you aren't familiar with the tnsnames.ora file I would not edit it by hand.  Use the Oracle Network Configuration Assistant to create another alias.

Author Comment

ID: 16702973
Can you give a step by step instruction how to use the Oracle Network Configuration Assistant to create an 8 character alias for Oracle 10g????

your help will be very appreciated!!

Expert Comment

ID: 16707768
Dear geert Zaal
 For this you either have to change database sid using NID utility
Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.


Expert Comment

ID: 16707773
it will not work with tnsname change because veritas picks sid from machine
LVL 78

Expert Comment

by:slightwv (䄆 Netminder)
ID: 16708188
Thanks for clarifying that.  I was going from some very old and tired brain cells.  Can you continue to help geert_zaal with this?

Accepted Solution

haidersyed earned 2000 total points
ID: 16748784

1-  Shutdown Database
2-  Take a complete cold copy of database
3-  Shutdown immediate or startup nomount
4-  nid target="sys as sysdba" dbname=haider1
provide the password

Haider1 is the new dbname


Expert Comment

ID: 16748922
Please remember to create a pfile from spfile before new database creation
 and change dbname and instance_name in that Pfile
and startup mount with that pfile
after that open database with resetlogs


Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article started out as an Experts-Exchange question, which then grew into a quick tip to go along with an IOUG presentation for the Collaborate confernce and then later grew again into a full blown article with expanded functionality and legacy…
Using SQL Scripts we can save all the SQL queries as files that we use very frequently on our database later point of time. This is one of the feature present under SQL Workshop in Oracle Application Express.
This video explains at a high level with the mandatory Oracle Memory processes are as well as touching on some of the more common optional ones.
This video explains at a high level about the four available data types in Oracle and how dates can be manipulated by the user to get data into and out of the database.
Suggested Courses

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question