Continue to Site

Welcome to MCAD Central

Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.

Failed to Backup

I had tried to back up my intralink data server, I had started Pro Intralink DSMU, connect administration, go to backup/restore>>dataserver backup>>full, when Ilink ask for pw, I had supplied internal (user name is also internal and I cant change it) after this stage I got this msg.
 
To be honest I've never used this method. I don't like it. Sometimes the error isn't with you it's with DSMU.

Instead, be sure everyone has checked in, lock the database as read-only (if you have to do this during the day) and then run the ilink_export.bat to create a dump file.

copy the dump file and the vault directory as your backup.
 
Hey Zaki,

If you want to be able to use the interface you will probably need to add "internal" to the database users list with "Administrative (using Windows term)" privleges. I will test out a method and post it probably later on tonight or tomarrow.

With regards to the ilink_export.bat command line usage, be careful, with me sometimes I need to manually specify a privledged username and password as one of the flags in the command. This may apply to any of the Pro/Intralink adminstrative batch files. Only do this if you attempt to run a batch file and it gives you a "Failed login" error (similar to your error above but probably a different ORA-XXXXX error).

I do agree with provan though. Sometimes that DSMU can be a bear.

I will get back to you.
 
THANNX in advance Adam


u r so helpful
smiley32.gif
 
acook said:
With regards to the ilink_export.bat command line usage, be careful, with me sometimes I need to manually specify a privledged username and password as one of the flags in the command.

Not sure what you are meaning there. However, for any administrative tool you use you have to have the proper access. If you are using batch files, the best way to handle it is set it in the environment.

ora_sys_pwd=manager
fs_sys_pwd=fschangeme
proi_sys_pwd=dschangeme

the syntax for ilink_export.bat is:
ilink_export manager <path for dump file> i.e. ilink_export manager c:\dumpfile.dmp
 
Hey provan,

You may be right about ilink_export.bat. I don't know if its just that I am using an old build or soemthing (3/4 M011( but some of the batch files (if you look at the batch code) contain errors when dealing with system environment variables. The last time I remeber running into this was when I was setting up the SMTP settings for Intralink using the appropriate batch file. I have those environment variables set. Personally, I have only done a backup via DSMU not via ilink_export.bat.

Thanks.
 
Adam,

Interesting that you had an issue. I have the dump file being created on a backup schedule so as to not allow any open processes during the backup.

Because Oracle cannot be backed up while active (I don't even recall the OpenFile option being 100% successful) we have been using the dump file and data copy method for years. I have backups run every night.

I think that this is even the preferred method if you talk to PTC engineers. Also, it makes for easy migration/upgrade (without even bothering to use the useless migration function).

Cheers,
 

Sponsor

Back
Top