Re: ARCHIVE command - length restrictions

2001-03-05 Thread Richard Sims
>...The only way that TSM accepts wildcards is by using double quotes... You're confusing TSM and Unix shell actions. As long as TSM gets the wildcard characters, it can expand them. Whether the wildcard characters that you type actually get to TSM is a function of what command shell you are ru

Re: ARCHIVE command - length restrictions

2001-03-05 Thread Bernhard Unold
Perhaps you get a better result by using a backslash to mask the asterisk. We are using in our Oracle-save-script: dsmc archive -servername=$ADSMSERV -archmc=$ADSMCLASS -DELETEFILES -verbose /bigspace/\*$ORACLE_SID* >> $ORACLEPROT and it works. The script is not written by me, but as far i know al

Re: ARCHIVE command - length restrictions

2001-03-05 Thread Sergio Cherchyk
Hi Bernhard. > Any idea? Perhaps tsm doesn't want to search several files systems. You > can get the names of the filesystems with a simple df. > So perhaps you can archive '/TST11/data/*.dbf /TST11/data/*.dbf .' > and so on if /TST11/data and /TST11/data/ are filesystems. It's not the case

Re: ARCHIVE command - length restrictions

2001-03-04 Thread Rik Foote
Sergio, the "real" restriction on an ARCHIVE command is that you can only specify 20 objects to be archived, either directories or files. This does not appear in the v3.7 doco but was present in v3.1 where we first encountered it. Rik Foote ---

Re: ARCHIVE command - length restrictions

2001-03-02 Thread Bernhard Unold
dsmc h 30 gives the answer: ANS1081E Invalid search file specification 'string' entered. Explanation: You entered a file specification or search string that contains incorrect characters or contains wildcard characters in the drive specification or file system name. System Action: Processin

Re: ARCHIVE command - length restrictions

2001-03-01 Thread Sergio Cherchyk
Bernhard. Thanks for your reply. It seems to fit our requirements, if I manage myself to do it work properly. Unfortunately, I was busy these days so I didn't see your message until yesterday. I tested the command with the sintax that you gave me (cut & paste) but I cannot have it running as I exp

Re: ARCHIVE command - length restrictions

2001-02-23 Thread Richard Sims
> dsmc archive -archmc=ORACLE_DIARIO -desc="TST11 OFFLINE ORACLE_DIARIO > 20010216.153447" /oracle/rdbms/8.0.5/dbs/initTST11.ora > /TST11/dbs/system01.dbf /TST11/data/ajes_data.dbf > /TST11/data/amul_data.dbf /TST11/index/amul_ind.dbf > /TST11/rollback/rbs.dbf /TST11/temporary/temporary.dbf > /TST

Re: ARCHIVE command - length restrictions

2001-02-23 Thread Bernhard Unold
I don't know the real restriction. But i have a suggestion to avoid it. Check if you can use this dsmc archive -archmc=ORACLE_DIARIO -desc="TST11 OFFLINE ORACLE_DIARIO 20010216.153447" /oracle/rdbms/8.0.5/dbs/initTST11.ora '/TST11/*/*.dbf' The single quotes inhibits the shell to interpret the wild