Inaddition above user can change database,catalog or RAC credentials also for both windows on unix clients. Qoperation execscript -sn SetOracleCredentials.sql -si allclients -si t=Impersonate -p2 passwd -si domainname\username Qoperation execscript -sn SetOracleCredentials.sql -si c=client1 -si t=Impersonate -p2 passwd -si domainname\username SET = + ' DROP ASSEMBLY ' + CHAR(10)ĮXECUTE sp_executeSql the Oracle credentials for auto discovered instances.Īfter Auto discover Oracle Instances on windows to provide the user credentials please use the following syntax:(t=Impersonate is for only windows clients) SET = + 'IF EXISTS (SELECT name FROM sys.assemblies asms WHERE asms.name = N''dbCLR'') ' + CHAR(10) SELECT utility can be un-registered in the Database using following query in SQL Management Studio: SET = + 'WITH EXECUTE AS CALLER ' + CHAR(10) NVARCHAR(MAX), NVARCHAR(MAX) OUTPUT) ' + CHAR(10) SET = + 'CREATE ASSEMBLY dbCLR FROM N''' + + ''' WITH PERMISSION_SET = UNSAFE ' + CHAR(10)
SET = + 'IF NOT EXISTS (SELECT name FROM sys.assemblies asms WHERE asms.name = N''dbCLR'') ' + CHAR(10) ' + CHAR(10)ĮXECUTE sp_executeSql = 0 GOTO CX_EXIT SET = + 'IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N''.'') AND type IN (N''P'', N''PC'')) ' + CHAR(10) Give DATABASAE name where this procedure is needed. eg: C:\Program Files\CommVault\Simpana\Base\dbclr.dll SET = 'C:\Program Files\CommVault\Simpana\Base\DBCLR.DLL'-INPUT REQUERED. This utility can be registered in the Database using following query in SQL Management Studio: Provide the ability to run Simpana Qcommands directly from SQL native client tools. Installed on : CommCell Console, Web Server Qoperation execscript -sn SetLimitRunningJobs.sql -si 'myclient' -si 'View' Qoperation execscript -sn SetLimitRunningJobs.sql -si 'myclient' -si 'Exclude' -si 0 To disable the option to exclude immediate jobs for myclient: Qoperation execscript -sn SetLimitRunningJobs.sql -si 'myclient' -si 'Exclude' -si 1 To enable the option to exclude immediate jobs for myclient: Qoperation execscript -sn SetLimitRunningJobs.sql -si 'myclient' -si 'LogCount' -si 3 To set the maximum log job count as 3 for myclient: Qoperation execscript -sn SetLimitRunningJobs.sql -si 'myclient' -si 'DataCount' -si 5 To set the maximum data job count as 5 for myclient: Qoperation execscript -sn SetLimitRunningJobs.sql -si 'myclient' -si 'LimitJobs' -si 0 To disable the option to limit running jobs for myclient: Qoperation execscript -sn SetLimitRunningJobs.sql -si 'myclient' -si 'LimitJobs' -si 1 To enable the option to limit running jobs for myclient: ***** To enable\disable the client level option ***** Qoperation execscript -sn SetKeyIntoGlobalParamTbl.sql -si ThrottleJobsFeature -si n Qoperation execscript -sn SetKeyIntoGlobalParamTbl.sql -si ThrottleJobsFeature -si y -si 1 Use the script SetKeyIntoGlobalParamTbl to set the option in DB as shown below. The throttling feature has to be enabled by enabling the Global parameter option. ***** To enable\disable the whole feature ***** Oracle command line backups may fail intermittently at the start of the backupįor Fix 1, Please follow the following instructions to enable/disable job throttling. Installed on : CommServe Database, CommServe Database Value: time in minutes to wait for the first job to finish preparation before each job will run preparation on its own. Name: TIMEOUT_PREPARATION_PARALLEL_SNAPMINING To change this timeout set the following key By default the other snap mining jobs running parallel will wait up to 6 hours for that snap to be prepared before beginning the preparation on their own. In extreme cases the initial snap may take too long to prepare if log replay takes many hours. Value: time in minutes to wait between attempts to prepare the snapshot for concurrently running snap mining jobs. Location: \MSExchangeMBAgent or \MSExchangeMBDMAgent depending on the agent installed To change this timeout you can set the following key Messages with file attachments whose names contain Unicode characters (Russian, Japanese, etc.) were backed up with spaces in the name instead.īy default, snap mining jobs which will use the same set of snapshots as an already running job will wait for 15 minutes so the first job has a chance to prepare the snapshot.