Error comparing to catalogs using runcat.cmd

Hi,
I am trying to compare to catalogs using runcat.cmd, it gives me the below error.
Missing or bad option "-outputFile".
The syntax I use :
runcat.cmd -cmd diff -baseline c:\sample1 -latest c:\sample2 -outputfile c:\output1.txt -folder /shared -verbosity detail
Example in help:
runcat.cmd/runcat.sh -cmd diff -baseline c:\temp\eba795 -latest c:\temp\eba796 -outputFile c:\temp\diff.txt -folder /shared/Sales:/shared/Financials -verbosity detail
Need help on this.

Now I get a new error after chnaging -outputfile to -outputFile.
no sawjniapi3r in java.library.path
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.siebel.analytics.web.catalogmanager.commands.Command.runCmd(Comma
nd.java:469)
at com.siebel.analytics.web.catalogmanager.commands.Command.processCmdLi
ne(Command.java:700)
at com.siebel.analytics.web.catalogmanager.CatalogManager.start(CatalogM
anager.java:36)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandl
e.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runAppli
cation(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Ec
lipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.ja
va:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.ja
va:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
Caused by: java.lang.UnsatisfiedLinkError: no sawjniapi3r in java.library.path
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at com.siebel.analytics.web.catalogmanager.JNIConnection.init(JNIConnect
ion.java:84)
at com.siebel.analytics.web.catalogmanager.JNIConnection.<init>(JNIConne
ction.java:25)
at com.siebel.analytics.web.catalogmanager.OfflineConnectionManager.<ini
t>(OfflineConnectionManager.java:29)
at com.siebel.analytics.web.catalogmanager.PluginManager.activate(Plugin
Manager.java:62)
at com.siebel.analytics.web.catalogmanager.PluginManager.connect(PluginM
anager.java:77)
at com.siebel.analytics.web.catalogmanager.commands.Command.login(Comman
d.java:1605)
at com.siebel.analytics.web.catalogmanager.commands.DiffCommand.run(Diff
Command.java:185)

Similar Messages

Error while packing domain using pack.cmd

Hi,
I am trying to pack my domain from HOST A using command :
pack -managed=true -domain=C:\Oracle\Middleware\user_projects\domains\Edlink -template=C:\Oracle\edlink.jar -log=c:\oracle\edlink.log -template_name="template_name"
and wants to unpack it on HOST B
But I am able to see below errors in my pack log file:
2014-09-01 16:52:57,825 INFO [runScript] com.bea.plateng.domain.script.ScriptExecutor - read domain from "C:\Oracle\Middleware\user_projects\domains\Edlink"
2014-09-01 16:52:59,672 ERROR [runScript] com.bea.plateng.domain.jdbc.TemplateDatabaseInfoHelper - FATAL ERROR: database.xml validation error!
2014-09-01 16:52:59,673 ERROR [runScript] com.bea.plateng.domain.jdbc.TemplateDatabaseInfoHelper - database XML parsing failed: error: cvc-complex-type.2.4a: Expected element 'sql-statement@http://xmlns.oracle.com/weblogic/template-database' instead of 'datasource-mapping@http://xmlns.oracle.com/weblogic/template-database' here in element test@http://xmlns.oracle.com/weblogic/template-database
2014-09-01 16:52:59,673 ERROR [runScript] com.bea.plateng.domain.jdbc.TemplateDatabaseInfoHelper - fail to parse database.xml
java.lang.Exception: Database.xml validation failed.
at com.bea.plateng.domain.jdbc.TemplateDatabaseInfoHelper.parseTemplateDatabaseInfo(TemplateDatabaseInfoHelper.java:582)
at com.bea.plateng.domain.TemplateBuilder.parseDomainDirectory(TemplateBuilder.java:835)
at com.bea.plateng.domain.TemplateBuilder.buildDomainTemplate(TemplateBuilder.java:1342)
at com.bea.plateng.domain.TemplateBuilder.buildNewDomainTemplate(TemplateBuilder.java:1287)
at com.bea.plateng.domain.TemplateBuilder.buildNewDomainTemplate(TemplateBuilder.java:1279)
at com.bea.plateng.domain.script.ScriptExecutor.readTemplate(ScriptExecutor.java:416)
at com.bea.plateng.domain.script.ScriptParserClassic$StateMachine.processRead(ScriptParserClassic.java:524)
at com.bea.plateng.domain.script.ScriptParserClassic$StateMachine.execute(ScriptParserClassic.java:428)
at com.bea.plateng.domain.script.ScriptParserClassic.parseAndRun(ScriptParserClassic.java:150)
at com.bea.plateng.domain.script.ScriptParserClassic.doExecute(ScriptParserClassic.java:113)
at com.bea.plateng.domain.script.ScriptParser.execute(ScriptParser.java:73)
at com.bea.plateng.domain.script.ScriptParser.execute(ScriptParser.java:36)
at com.bea.plateng.wizard.domain.helpers.Executor.runSilentScript(Executor.java:66)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.plateng.wizard.domain.silent.tasks.RunScriptTask.runScriptWithExecutor(RunScriptTask.java:552)
at com.bea.plateng.wizard.domain.silent.tasks.RunScriptTask.execute(RunScriptTask.java:336)
at com.bea.plateng.wizard.silent.tasks.AbstractSilentTask.run(AbstractSilentTask.java:28)
at java.lang.Thread.run(Thread.java:662)
2014-09-01 16:53:00,446 WARN [runScript] com.bea.plateng.domain.aspect.XBeanConfigAspect - Unable to locate property:Target on type:class com.bea.plateng.domain.xml.configxb.impl.MachineTypeImpl
2014-09-01 16:53:00,451 WARN [runScript] com.bea.plateng.domain.aspect.XBeanConfigAspect - Unable to locate property:Target on type:class com.bea.plateng.domain.xml.configxb.impl.ClusterTypeImpl
2014-09-01 16:53:00,451 WARN [runScript] com.bea.plateng.domain.aspect.XBeanConfigAspect - Unable to locate property:Target on type:class com.bea.plateng.domain.xml.configxb.impl.ServerTypeImpl
2014-09-01 16:53:00,451 WARN [runScript] com.bea.plateng.domain.aspect.XBeanConfigAspect - Unable to locate property:Target on type:class com.bea.plateng.domain.xml.configxb.impl.ServerTypeImpl
2014-09-01 16:53:00,482 INFO [runScript] com.bea.plateng.domain.script.ScriptExecutor - succeed: read domain from "C:\Oracle\Middleware\user_projects\domains\Edlink"
2014-09-01 16:53:00,484 INFO [runScript] com.bea.plateng.domain.script.ScriptExecutor - set config option Managed to "true"
2014-09-01 16:53:00,532 INFO [runScript] com.bea.plateng.domain.script.ScriptExecutor - succeed: set config option Managed to "true"
2014-09-01 16:53:00,534 INFO [runScript] com.bea.plateng.domain.script.ScriptExecutor - write template to "C:\Oracle\edlink.jar"
2014-09-01 16:53:03,449 INFO [Thread-1] com.bea.plateng.domain.TemplateGenerator - Template Generation Successfull!
2014-09-01 16:53:03,480 INFO [runScript] com.bea.plateng.domain.script.ScriptExecutor - succeed: write template to "C:\Oracle\edlink.jar"
2014-09-01 16:53:03,481 INFO [runScript] com.bea.plateng.domain.script.ScriptExecutor - close template
2014-09-01 16:53:03,481 INFO [runScript] com.bea.plateng.domain.script.ScriptExecutor - succeed: close template
I have faced this problem earlier also but that time I used tar.sh and untar.sh scripts provided by our engineering team, but this time I don't have.
also it seems there is some ongoing bug with pack.sh/cmd & unpack.sh/cmd
thus it fails to compress the domain into a jar everytime
FYI: I am using
WebLogic server with portal 10.3.2
with DB as MSSQL Server
on windows platform
Solution to this post would be appreciable.
Thanks
Punit

The issue seems to be similar to this bug:
Bug 13624207 - ISSUE WHEN USING PACK/UNPACK COMMAND WHILE CREATING DOMAIN USING WLST.
Please try posting here:
WebLogic Portal
Best Regards
Luz

Error exporting catalog using bi_export.bat

Getting error when exporting catalog using bi_export.bat
version 9.2.0.2
bi_export -u BIBCAT -p BIBCAT -j thin -h localhost -po 1521 -sid mysid -x a catalogdump.xml
Fri Feb 28 14:40:31 CET 2003 PROBLEM: In oracle.dss.persistence.administration.Export::StorageManager InitializeStorageManager(String classname, Hashtable env): BIB-14418 Loaded storagemanager: oracle.dss.persistence.storagemanager.bi.BIStorageManagerImpl
Any idea?
-peter

Hi Folks,
I tested this on my server and I got the same error and no XML file created. However, in the documentation there is an additional switch that identifies the logical user and when this is used the XML file should be created. There is still a warning message issued BIB-14418, however, as Katia has identified this is expected behaviour.
So the command that works for me is as follows:
bi_export -u BIBCAT -p BIBCAT -lu BIBCAT -j thin -h localhost -po 1521 -sid mysid -x a catalog.xml
The TAR listed above has been updated by support to reflect this information as well. Hope this helps.
Keith Laker
Product Manager
Oracle Business Intelligence Beans

Unrecoverable error generating exported catalog

I am getting an unrecoverable error when trying to export the whole catalog from 1.3 (error also occurs on the new 1.3.1)
the error message is unrecoverable error generating exported catalog
I have also tried to import the catalog into a new catalog and export that but that still gives the same error.
this error is occurring when I try to export all the photos in the catalog.
Any help would be grateful in correcting this error as I really need to export the whole database to my external drive for a trip thats coming up in a week.
Cheers

I was also getting the "unrecoverable error generating exported catalog" using Lightroom 1.3.1 on WinXP from a particular catalog (I could export from other catalogs fine). It didn't matter if I was exporting one image or 1000, it still failed with the same, useless, "something really bad happened" error message.
I tried optimizing, doing integrity checks, but still no dice. What did work, though, was to create a new (empty) catalog, then import the suspect catalog (if your catalog is big, expect a long wait). I was then able to do my export successfully from the new (hopefully equivalent) catalog. I'll make the new catalog my primary after assuring myself that I didn't lose anything in the process.
Of course, YMMV, but it's worth a try.
-Don

Trying to register 10.2.0.3 db in Rec Catalog using OEM, getting errors

Hi all,
I didn't know whether to post this here in the RMAN forum or in the OEM Grid Control forum, but the issue is more related to RMAN, so I'll post it here, and hope someone can help me out!
I have a new 10.2.0.3 database that I am getting configured to manage using OEM Grid Control. Through the OEM interface, I am trying to register this database with my recovery catalog - the recovery catalog is version 10.02.00.02. When I try to register this new db with the recovery catalog, I am getting this lengthy collection of errors:
Recovery Manager: Release 10.2.0.3.0 - Production on Wed Jan 30 14:58:36 2008 Copyright (c) 1982, 2005, Oracle. All rights reserved. RMAN> connected to target database: INSIGHT (DBID=4016731035) RMAN> connected to recovery catalog database PL/SQL package RMAN.DBMS_RCVCAT version 10.02.00.02 in RCVCAT database is not current PL/SQL package RMAN.DBMS_RCVMAN version 10.02.00.02 in RCVCAT database is not current RMAN> echo set on RMAN> register database; RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of register command at 01/30/2008 14:58:40 RMAN-06004: ORACLE error from recovery catalog database: ORA-06550: line 1, column 2453: PLS-00302: component 'RESTORECMD_T' must be declared ORA-06550: line 1, column 2424: PL/SQL: Statement ignored RMAN> exit; Recovery Manager complete.
It sounds like it has something to do with the fact that my recovery catalog database is not at a current version?? In the OEM tool, I went to the page that lists the Recovery Catalog, and tried hitting the Update button, and it succeeded, but the Recovery Catalog version did not change, it is still at 10.02.00.02.
Can anyone give me some assistance on this one?
Thanks!
--Brad

Hi,
please check with
select comp_name,status,version from dba_registry;
COMP_NAME
STATUS VERSION
Oracle Database Catalog Views
VALID 10.2.0.3.0
Oracle Database Packages and Types
UPGRADED 10.2.0.3.0
The UPGRADED status is not good. Run utlrp.sql again and then again as rman user the "upgrade catalog". Now it should work fine.
Bye
Matthias

Crystal report Error for CRVS2010 sp2 using Push Method

I am trying to pass a dataset to a crystal report viewer using SetDatabaseSource.
I have defined in Crystal to used an ADO .Net Database XML Schema.
I pass a Dataset to the Report By using SetDatbaseSourece and set the ReportSource for the CrystalViewer but I get the error that crdb_adoplus.dll does not exists.
Note that Crystal is looking for crdb_adoplus.dll under subdirectory dotnet1. It resides under win32_x86.
Is this a Crystal Report Problem ?
Is their any docuentation that show how to program for ADO xml dataset using crvs2010 ?
The Error Reads
System.IO.FileNotFoundException was unhandled
Message=Could not load file or assembly 'file:///C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dotnet1\crdb_adoplus.dll' or one of its dependencies. The system cannot find the file specified.
Source=mscorlib
FileName=file:///C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dotnet1\crdb_adoplus.dll
FusionLog==== Pre-bind state information ===
LOG: User = WKST04\GARYB
LOG: Where-ref bind. Location = C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dotnet1\crdb_adoplus.dll
LOG: Appbase = file:///D:/S_and_G/LMS_DotNet/LMS_Solution/LMS/bin/Debug/
LOG: Initial PrivatePath = NULL
Calling assembly : (Unknown).
===
LOG: This bind starts in LoadFrom load context.
WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load().
LOG: Using application configuration file: D:\S_and_G\LMS_DotNet\LMS_Solution\LMS\bin\Debug\LMS.vshost.exe.Config
LOG: Using host configuration file:
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: Attempting download of new URL file:///C:/Program Files (x86)/SAP BusinessObjects/Crystal Reports for .NET Framework 4.0/Common/SAP BusinessObjects Enterprise XI 4.0/win32_x86/dotnet1/crdb_adoplus.dll.
StackTrace:
       at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
       at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
       at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection, Boolean suppressSecurityChecks)
       at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
       at System.Reflection.Assembly.LoadFrom(String assemblyFile)
       at CrystalDecisions.ReportAppServer.DataSetConversion.DataSetConverter.DataSetProcessingDelegate(IntPtr arg)
InnerException:

Microsoft Visual Studio 2010 Version 10.0.40219.1 SP1Rel
Crystal Reports for .NET Framework 4.0 (CRforVS_13_0_2)
project WPF net 4.0
crReport = new Reports.Buh.Cma.cr_balances_cma_move();
using (DataTable tbl = new DataTable())
   using (SqlConnection cn = new SqlConnection(ConnectToDataBase.GetSqlConnectionString()))
         using (SqlCommand cmd = cn.CreateCommand())
                cmd.CommandText = "proc_name";
                cmd.CommandType = CommandType.StoredProcedure;
                using (SqlDataAdapter da = new SqlDataAdapter(cmd))
                        cn.Open();
                        da.Fill(tbl);
crReport.SetDataSource(tbl);
crReport.SetParameterValue(4, param["report_name"]);
myDateTime.GetServerDate();
crReport.SummaryInfo.ReportAuthor = App.GetPrintInfo();
e.Result = crReport;
erorr_message - Could not load file or assembly 'file:///C:\Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dotnet1\crdb_adoplus.dll' or one of its dependencies. Не удается найти указанный файл.
help plz

RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

Good Morning All,
One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
==================================================================================================
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
====================================================================================================
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: CUSTPR (DBID=525071053)
RMAN>
RMAN> #########################################################################
2> # LEVEL 0 BACKUP #
3> #########################################################################
4>
5> # Configure backups to be written to disk.
6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
2> # RMAN retains all backups needed to recover the database to any point in time
3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
4> # backups that are no longer required by the retention policy. To exclude a
5> # backup from consideration by the policy, you can use KEEP option with the
6> # BACKUP command.
7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
2> # maintenance operations.
3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write disk backups to the /backup directory.
2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
3> # backup set number, and %p with the backup piece number.
4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to back up the control file after each backup.
2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
2> # RMAN won't backup an archivelog or datafile if there already exists a backup
3> # of that file. The FORCE option can be used to override optimization on a
4> # specific BACKUP command.
5> CONFIGURE BACKUP OPTIMIZATION ON;
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Use the SHOW ALL command to see the current configuration settings.
2> SHOW ALL ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
RMAN>
RMAN> # The following commands are run each day to start the backup cycle.
2> # The steps are:
3> # - Take an incremental level 0 backup of the database. A level 0 backup is
4> # a complete backup of the entire file which can be used as the basis
5> # for a subsequent incremental backup.
6> # - Backup all archivelogs that have not already been backed up.
7> # - Delete on-disk archivelogs older than seven days.
8>
9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
10> DATABASE maxsetsize 33G
11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
12> delete all input;
Starting backup at 12/30/2008 22:01:40
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
Finished backup at 12/30/2008 22:03:47
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Recovery Manager complete.

Runtime error in Field catalog creation

when i try to create the field catalog using the following code.
am getting *'Field Symbol Is not assigned' Runtime error.*
Please give me idea how to resolve this issue.
data: wa_field type slis_fieldcat_alv,
        t_field type slis_t_fieldcat_alv.
LOOP AT t_role INTO wa_role.
    wa_field-col_pos = count1.
    wa_field-fieldname = wa_role-agr_name.
    wa_field-datatype = 'CHAR'.
    wa_field-ref_fieldname = 'AGR_NAME'.
    wa_field-ref_tabname = 'AGR_1251'.
    APPEND wa_field TO t_field.
    count1 = count1 + 1.
ENDLOOP.
Suitable Answers rewarded with maximum points....
it's Urgent...
Give me Quick Reply.

Error is having following short text.
Field symbol has not yet been assigned.
Error analysis
    You attempted to access an unassigned field symbol
    (data segment 92).
This error may occur for any of the following reasons:
    - You address a typed field symbol before it is set using ASSIGN
    - You address a field symbol that points to a line in an internal table
      that has been deleted
    - You address a field symbol that had previously been reset using
      UNASSIGN, or that pointed to a local field that no longer exists
    - You address a global function interface parameter, even
      though the relevant function module is not active,
      that is it is not in the list of active calls. You can get the list
      of active calls from the this short dump.
Please tell me how to correct this error.
It is very Urgent..

Error in Accessing Catalog

Hi,
I get an error while accessing the catalog in the SHC page. I have the screenshots of the error. Request help in trying to find out the cause for this.

Hi
I am still looking for more details.
<u>Meanwhile, Please try the following OSS Notes.</u>
<b>Note 871302 - Unable to switch between catalogs using F4 help
Note 890967 - /CCM/CHECK_TREX shows incorrect document content
Note 946185 - CCM20: /CCM/CHECK_TREX modifications
Note 707781 - Product search does not find all documents
Note 481295 - Short dump RAISE_EXCEPTION when expanding a product node
Note 723688 BBP TREX corrections for SRM 4.0 SP01
Note 778688 TREX_INDEX_MANAGER unit test update_view(): incorrect search
Note 930788 - Search help for catalog does not display all catalogs
Note 1028343 Changes in the repository not reflected in Catalog UI
Note 1015201 - SRM-MDM Catalog 1.0 Patch02 Release Note
Note 487917 BADI implementation f. BBP_CATALOG_CONTENT (Troubleshooting)
Note 877131 Product category is not permitted for the user
Note 623067 SRM 2.0 Integrated Catalog does not display catalog info
</b>
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Boot permission error starting managed server using startManagedWebLogic

Hello
          I have a clustered WLS environment and am having problems starting the managed server from the command line using startManagedWebLogic.cmd script. The managed server starts without any problems from the admin console. Using the startManagedWebLogic.cmd script and the same login as I use for admin console, I am getting the following error when I execute:
          startManagedWebLogic MyServer http://localhost:7001
          Error displayed is:
          <09-Aug-2005 14:21:46 o'clock BST> <Critical> <Security> <BEA-090404> <User vgnadmin is no
          t permitted to boot the server; The server policy may have changed in such a way that the
          user is no longer able to boot the server.Reboot the server with the administrative user a
          ccount or contact the system administrator to update the server policy definitions.>
          The WebLogic Server did not start up properly.
          Reason: weblogic.security.SecurityInitializationException: User vgnadmin is not permitted
          to boot the server; The server policy may have changed in such a way that the user is no l
          onger able to boot the server.Reboot the server with the administrative user account or co
          ntact the system administrator to update the server policy definitions.
          Has anyone come accross this problem before? What can I do to run the managed server from command line?
          My environment details:
          OS: Windows 2000 Server SP3
          WebLogic Server 8.1 SP2 (clustered with a single node)
          Thanks in advance for your help.

I have the same issue. However I am using ALES (Weblogic Enterprise Security) with WLS SP3.
          Mine could be an ALES specific issue. Let me know if you have any updates.

Error in uploading catalog

Hi Gurus,
One of user is getting problem in uploading catalogs in SRM system - Following are the error logs -
Uploading catalog GLOBAL_ECOMPANYSTORE
Name of file that was uploaded: D:\Profiles\JCAPOZZI\My Documents\BIN\eCompanyStore Content Catalog_datase V54.csv
2007/10/12 18:19:55 (GMTUK): Starting CSV import for catalog GLOBAL_ECOMPANYSTORE
2007/10/12 18:19:56 (GMTUK): 0001 package(s) were processed OK
2007/10/12 18:19:56 (GMTUK): Package 0001 received and saved
2007/10/12 18:19:56 (GMTUK): schema locked; number of lock attempts remaining: 59
2007/10/12 18:20:56 (GMTUK): schema locked; number of lock attempts remaining: 58
2007/10/12 18:21:56 (GMTUK): schema locked; number of lock attempts remaining: 57
2007/10/12 18:22:56 (GMTUK): schema locked; number of lock attempts remaining: 56
2007/10/12 18:23:56 (GMTUK): schema locked; number of lock attempts remaining: 55
2007/10/12 18:24:56 (GMTUK): schema locked; number of lock attempts remaining: 54
2007/10/12 18:25:56 (GMTUK): schema locked; number of lock attempts remaining: 53
2007/10/12 18:26:56 (GMTUK): schema locked; number of lock attempts remaining: 52
2007/10/12 18:27:56 (GMTUK): schema locked; number of lock attempts remaining: 51
2007/10/12 18:28:56 (GMTUK): schema locked; number of lock attempts remaining: 50
2007/10/12 18:29:56 (GMTUK): schema locked; number of lock attempts remaining: 49
2007/10/12 18:30:56 (GMTUK): schema locked; number of lock attempts remaining: 48
2007/10/12 18:31:56 (GMTUK): schema locked; number of lock attempts remaining: 47
2007/10/12 18:32:56 (GMTUK): schema locked; number of lock attempts remaining: 46
2007/10/12 18:33:56 (GMTUK): schema locked; number of lock attempts remaining: 45
2007/10/12 18:34:56 (GMTUK): schema locked; number of lock attempts remaining: 44
2007/10/12 18:35:56 (GMTUK): schema locked; number of lock attempts remaining: 43
2007/10/12 18:36:56 (GMTUK): schema locked; number of lock attempts remaining: 42
2007/10/12 18:37:56 (GMTUK): schema locked; number of lock attempts remaining: 41
2007/10/12 18:38:56 (GMTUK): schema locked; number of lock attempts remaining: 40
2007/10/12 18:39:56 (GMTUK): schema locked; number of lock attempts remaining: 39
2007/10/12 18:40:56 (GMTUK): schema locked; number of lock attempts remaining: 38
2007/10/12 18:41:56 (GMTUK): schema locked; number of lock attempts remaining: 37
2007/10/12 18:42:56 (GMTUK): schema locked; number of lock attempts remaining: 36
2007/10/12 18:43:56 (GMTUK): schema locked; number of lock attempts remaining: 35
2007/10/12 18:44:56 (GMTUK): schema locked; number of lock attempts remaining: 34
2007/10/12 18:45:56 (GMTUK): schema locked; number of lock attempts remaining: 33
2007/10/12 18:46:56 (GMTUK): schema locked; number of lock attempts remaining: 32
2007/10/12 18:47:56 (GMTUK): schema locked; number of lock attempts remaining: 31
2007/10/12 18:48:56 (GMTUK): schema locked; number of lock attempts remaining: 30
Catalog update was terminated
the job is getting terminated.
Please suggest and will surely give points for your responses.
Regards
Sridher

Raghu,
Carefully review your data to make sure eveything lines up and is appropriate. Then generate a new template and make sure it has all components in it even though you might not use everything. Then use the 'transfer" function to transfer the data from the existing file to the new template.
Try that. Sometimes MDUG will throw strange errors is you reuse files or copy them. Start with a clean template and this will hopefully work. This has worked for me in the past when I'd see strange, never seen before errors.
Thanks.
Matt

Error. Lightroom catalog can't open

Hello I keep getting the error: 'The Lightroom catalog named Lightroom 5 catalog cannot be opened because another application already has it opened' when opening Lightroom. There is no other application using it. there is only one file available, no back up as I have been uploading a 5.3TB catalogue over the past 4 days and didn't shut down. the RAW files sit on a separate hard drive to the laptop where the Lightroom catalogue is. I cannot now access that catalogue. I had a crash prior to this happening ... can anyone help out there?

I just wonder whether it was GB not TB!!!!
JimHess wrote:
Good grief! That flew right by me. That is one huge catalog. I wonder if there is a "practical" limit to catalog size.Or I wonder if this is terminology confusion. Catalog size vs. library size.

Unable to use endeca-cmd against the running Endeca Server

Hello Endeca forum,
I'm working in a client environment in which I can see that the Endeca Server is running:
1. Going to a browser on the server itself, I can see a positive result page when I go to http://localhost:7770/admin/<datasource>?op=ping
2. When I'm in the linux server and do a "ps -ef | grep "start", I see that there is a process running the server with "-Djetty.port=7770"
3. Studio running on the same server has datasources pointing at localhost:7770 (and Studio is showing data)
However, when I go to the endeca-cmd and try to create a new datasource ("./endeca-cmd create-ds <new_datasource_name>"), I see the following error:
"*Error contacting the Endeca Server localhost:7770: com/endeca/opmodel/opSupport/MkMdexRunner*"
I get the same error if I try to use a graph in Data Integrator with the "Create Data Store" component (taken from the quickstart InitDataStore.grf, but pointing to the client's Endeca Server).
Running "./endeca-cmd version" gives me an equally cryptic error:
"*Error contacting the Endeca Server localhost:7770: com/endeca/mdex/admin/_1/Admin*"
Has anyone seen this before?
I'm starting to think that this may be a strange environment issue, but I can't figure why I'd be able to see the server running through other means, but fail to interact with the server using endeca-cmd.
Thanks,
Jerome

Hey Brett,
Good points. Unfortunately, I can't install SoapUI on the client's server (where the Endeca Server is running), but I was able to run a graph that tries to create a dgraph on it (which is an HTTP call to the createDataStore operation). This call resulted in the same error that I saw when invoking "endeca-cmd create-ds". However, the failure of the graph gives me a little more in the form of a partial stack trace...
org.apache.axis2.AxisFault: com/endeca/opmodel/opSupport/MkMdexRunner
at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:451)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
... which doesn't really tell me anything.
Is there a place where I can see logs for the Endeca Server? Might be able to get a little more from a full stack trace...
I know that dgraph logs are at…
<OEID_installation>/Server/2.3.0/endeca-server/logs
But obviously these don’t hold anything about the dgraph that I’m trying to create.
Thanks,
Jerome

VS 2013 Build tools installation fails with error "Signature or catalog could not be verified"

VS 2013 ultimate - Build tools installation fails with error "Signature or catalog could not be verified" for MSBuild assemblies. Any idea what could be the problem?
Thanks
NM

Hello,
Do you mean you are trying to use this tool:
https://www.microsoft.com/en-us/download/details.aspx?id=40760
Can you navigate to your %temp% folder and filter by date to see the log of the Build tool?
I want to know which assemblies failed to be verified.
By the way, since MSBuild is embed in Visual Studio why you want to install this again? Do you have any error about this Build Tool when you install Visual Studio 2013 Ultimate?
“Signature or catalog could not be verified” is always related to corrupt source
, please double check you have a healthy network and then try the web installer again.
Best regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

ORA-01339: LogMiner BUILD: Error copying system catalog metadata to LogMiner

Hi, has anyone ever got this error in 11.2.0.3 primary database while trying to convert a physical standby to a logical standby?
Thanks

Per the documentation:
4.2 Step-by-Step Instructions for Creating a Logical Standby Database
Creating a Logical Standby Database
4.2.2 Stop Redo Apply on the Physical Standby Database
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
4.2.3.1 Prepare the Primary Database for Role Transitions
Has you adjust primary database init.ora parameters to be prepared for switchovers.
4.2.3.2 Build a Dictionary in the Redo Data
SQL> EXECUTE DBMS_LOGSTDBY.BUILD;
this puts a Multi-vertion Data Dictionary (MVDD) is the archive logs that are sent to the standby.
This is what fails with:
SQL> exec dbms_logstdby.build ;
BEGIN dbms_logstdby.build ; END;
ERROR at line 1:
ORA-01339: LogMiner BUILD: Error copying system catalog metadata to LogMiner dictionary
ORA-06512: at "SYS.DBMS_LOGMNR_INTERNAL", line 5972
ORA-06512: at "SYS.DBMS_LOGMNR_INTERNAL", line 6070
ORA-06512: at line 1
4.2.4.1 Convert to a Logical Standby Database
SQL> SHUTDOWN ABORT;
SQL> STARTUP MOUNT EXCLUSIVE;
SQL> ALTER DATABASE RECOVER TO LOGICAL STANDBY db_name;
this consumes the data dictionary into the standby for convertion. It is used by SQL apply to understandby object id's because the standby does not know the names of the objects that are in the primary database.
then you add some logical standby parameters and open the database and start SQL apply.
SQL> ALTER DATABASE OPEN RESETLOGS;
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
So running EXECUTE DBMS_LOGSTDBY.BUILD; is a standby alone process that can be tested any time. It does nothing to the primary except extract dictionary information and puts it in the archive logs.
I find no information on DBMS_LOGSTDBY.BUILD; ever failing. It must be specific to this primary database.
Thanks

Error comparing to catalogs using runcat.cmd

Similar Messages

Maybe you are looking for