XML installation on 8.1.7

Hi, I've posted this in the XML DB forum but I think that might have been the wrong place. So here goes again, might be a silly question but I need some way of confirming this so I can pass the info on to our DBA's.
Is there a quick way I check to see if XML has been setup on my database? I've been working on Oracle version 9.2 with some SQL/XML code. As soon as I've tried to copy it to our 8.1.7 database its not recognising any of the xml tags like DBMS_XMLQuery.getXML. I know there's some differences between database versions as to which tags it supports but I'm sure this one is supported in 8.1.7 so I'm starting to think that something hasn't been set up on the database. If this is the case what is it I need to instruct the DBA's to install?
thanks,
Ian

You might want to check out the following metalink notes:
Note 177411.1 How to identify the version of the XDK installed inside the database.
Note 156477.1 JVM installation on 8.1.7

Similar Messages

  • How to write a Xml installation file to build  web installer using IzPack.

    Hai everyone,
    I have got a problem in building a web installer using IzPack.I am getting this exception,when I am compiling my install.xml using a compile tool provided by IzPack soft.Eventhough I have not mentioned "packsinfo.xml" in my Xml installation file.
    Fatal error :
    null\packsinfo.xml (The system cannot find the path specified)
    java.io.FileNotFoundException: null\packsinfo.xml (The system cannot find the path specified)
    What went wrong??
    It is very very urgent. Could anyone tell me how to write a Xml installation file for building web installer,please??
    any help will be highly appreciated....
    Thank you very much in advance

    Hi,
    that is not really a java related question. Have you tried to find some IzPack support forum? I've never heard about it, so I can't help.

  • How to write a Xml installation file to build a web installer using IzPack.

    Hi Everybody,
    I am using IzPack 3.11.0 version.I'd like to create a web installer using IzPack.IzPack soft has provided one p.d.f. In
    which they has explained how to create a standard installer using xml installation file,however ,they have not explained
    how to create a web installer using xml installation file.
    Could anyone help me how to create a web installer using xml installation file,please?? It is very very urgent.
    Any help will be highly appreciated.Thank you very much in advance.

    Hi,
    that is not really a java related question. Have you tried to find some IzPack support forum? I've never heard about it, so I can't help.

  • XML DATABASE INSTALLATION

    i am installing xml database on live server with following step:-
    created tablespace
    create tablespace XDB datafile '/umsdata03/umsdb/datafile/ums_data_xdb01.dbf' size 1G;
    executing script
    @?/rdbms/admin/catqm.sql xdb123 XDB UMS_AUTOALLOC_TEMP
    but the script follow with error:-
    and pls suggest how to deal with port issue of xml installation
    SQL> create tablespace XDB datafile '/umsdata03/umsdb/datafile/ums_data_xdb01.dbf' size 1G;
    Tablespace created.
    SQL> SQL>
    SQL>
    SQL>
    SQL> @?/rdbms/admin/catqm.sql xdb123 XDB UMS_AUTOALLOC_TEMP
    CREATE TABLE sys.xdb_installation_tab (
    ERROR at line 1:
    ORA-00955: name is already used by an existing object
    CREATE TABLE sys.dropped_xdb_instll_tab (
    ERROR at line 1:
    ORA-00955: name is already used by an existing object
    DROP ON DATABASE
    ERROR at line 3:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-20000: Trigger xdb_installation_trigger does not support object creation of
    type TRIGGER
    ORA-06512: at line 32
    Trigger created.
    System altered.
    System altered.
    System altered.
    System altered.
    old 23: where tablespace_name = upper('&res_tbs');
    new 23: where tablespace_name = upper('XDB');
    old 29: where tablespace_name = upper('&temp_tbs');
    new 29: where tablespace_name = upper('UMS_AUTOALLOC_TEMP');
    old 47: raise_application_error(-20001, 'Compressed tablespace &res_tbs' ||
    new 47: raise_application_error(-20001, 'Compressed tablespace XDB' ||
    old 51: '&temp_tbs cannot be used');
    new 51: 'UMS_AUTOALLOC_TEMP cannot be used');
    PL/SQL procedure successfully completed.
    old 1: create user xdb identified by &xdb_pass account lock password expire
    new 1: create user xdb identified by xdb123 account lock password expire
    old 2: default tablespace &res_tbs temporary tablespace &temp_tbs
    new 2: default tablespace XDB temporary tablespace UMS_AUTOALLOC_TEMP
    User created.
    PL/SQL procedure successfully completed.
    old 1: create user anonymous identified by values 'anonymous' default tablespace &res_tbs
    new 1: create user anonymous identified by values 'anonymous' default tablespace XDB
    create user anonymous identified by values 'anonymous' default tablespace XDB
    ERROR at line 1:
    ORA-01920: user name 'ANONYMOUS' conflicts with another user or role name
    Grant succeeded.
    User altered.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    CREATE role xdbadmin
    ERROR at line 1:
    ORA-01921: role name 'XDBADMIN' conflicts with another user or role name
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Session altered.
    Table created.
    Table created.
    Index created.
    Type created.
    Table created.
    Index created.
    Type created.
    Type created.
    Type created.
    Synonym created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Index created.
    Index created.
    Index created.
    Table analyzed.
    Sequence created.
    Sequence created.
    Grant succeeded.
    Library created.
    Function created.
    Package created.
    No errors.
    Package body created.
    No errors.
    Procedure created.
    Function created.
    Grant succeeded.
    Grant succeeded.
    PL/SQL procedure successfully completed.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Grant succeeded.
    Type created.
    Grant succeeded.
    Table created.
    Table altered.
    Table altered.
    Index created.
    Table created.
    Index created.
    Index created.
    Index created.
    Package created.
    No errors.
    Package body created.
    No errors.
    PL/SQL procedure successfully completed.
    Session altered.
    Package created.
    No errors.
    Synonym created.
    Grant succeeded.
    Package created.
    Synonym created.
    Grant succeeded.
    No errors.
    Type created.
    No errors.
    Grant succeeded.
    Package created.
    No errors.
    Synonym created.
    Grant succeeded.
    No errors.
    drop type xdb.xdbpi_im
    ERROR at line 1:
    ORA-04043: object XDBPI_IM does not exist
    drop table xdb.xdb$path_index_params
    ERROR at line 1:
    ORA-00942: table or view does not exist
    Library created.
    Table created.
    Package created.
    Grant succeeded.
    No errors.
    Type created.
    No errors.
    Type body created.
    No errors.
    Grant succeeded.
    Package created.
    Package body created.
    Package created.
    No errors.
    Grant succeeded.
    Package created.
    Synonym created.
    No errors.
    Grant succeeded.
    Library created.
    Procedure created.
    No errors.
    Grant succeeded.
    Function created.
    No errors.
    Grant succeeded.
    Warning: Package Body created with compilation errors.
    No errors.
    Grant succeeded.
    No errors.
    Trigger created.
    No errors.
    Package body created.
    Package created.
    No errors.
    Synonym created.
    Synonym created.
    Synonym created.
    Grant succeeded.
    Grant succeeded.
    No errors.
    Package created.
    No errors.
    Synonym created.
    Synonym created.
    Synonym created.
    Grant succeeded.
    Grant succeeded.
    No errors.
    Package created.
    No errors.
    Package created.
    Synonym created.
    Synonym created.
    Synonym created.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    No errors.
    Grant succeeded.
    Library created.
    Package body created.
    No errors.
    Library created.
    Warning: Package Body created with compilation errors.
    No errors.
    Synonym created.
    Grant succeeded.
    No errors.
    Library created.
    Warning: Package Body created with compilation errors.
    No errors.
    Warning: Package Body created with compilation errors.
    Synonym created.
    Grant succeeded.
    No errors.
    Grant succeeded.
    Library created.
    Function created.
    Grant succeeded.
    Synonym created.
    Procedure created.
    No errors.
    Grant succeeded.
    Grant succeeded.
    Function created.
    No errors.
    Grant succeeded.
    Function created.
    Grant succeeded.
    Grant succeeded.
    Package body created.
    No errors.
    Warning: Package Body created with compilation errors.
    No errors.
    Synonym created.
    Grant succeeded.
    No errors.
    PL/SQL procedure successfully completed.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    Commit complete.
    Index created.
    Index created.
    Index created.
    Index created.
    Index created.
    Index created.
    Index created.
    Index created.
    Package created.
    No errors.
    Grant succeeded.
    Package body created.
    Package body created.
    No errors.
    Procedure created.
    No errors.
    Procedure created.
    No errors.
    drop view xdb.xdb$resource_view
    ERROR at line 1:
    ORA-00942: table or view does not exist
    drop view xdb.xdb$rv
    ERROR at line 1:
    ORA-00942: table or view does not exist
    PL/SQL procedure successfully completed.
    drop indextype xdb.xdbhi_idxtyp force
    ERROR at line 1:
    ORA-29833: indextype does not exist
    drop operator xdb.path force
    ERROR at line 1:
    ORA-29807: specified operator does not exist
    drop operator xdb.depth force
    ERROR at line 1:
    ORA-29807: specified operator does not exist
    drop operator xdb.abspath force
    ERROR at line 1:
    ORA-29807: specified operator does not exist
    drop operator xdb.under_path force
    ERROR at line 1:
    ORA-29807: specified operator does not exist
    drop operator xdb.equals_path force
    ERROR at line 1:
    ORA-29807: specified operator does not exist
    drop package xdb.xdb_ancop
    ERROR at line 1:
    ORA-04043: object XDB_ANCOP does not exist
    drop package xdb.xdb_funcimpl
    ERROR at line 1:
    ORA-04043: object XDB_FUNCIMPL does not exist
    drop type xdb.xdbhi_im
    ERROR at line 1:
    ORA-04043: object XDBHI_IM does not exist
    drop type xdb.path_array
    ERROR at line 1:
    ORA-04043: object PATH_ARRAY does not exist
    Library created.
    Library created.
    Type created.
    Type created.
    No errors.
    Grant succeeded.
    Grant succeeded.
    Type created.
    No errors.
    Type body created.
    No errors.
    Grant succeeded.
    Package created.
    No errors.
    Grant succeeded.
    Package created.
    No errors.
    Grant succeeded.
    Type altered.
    Operator created.
    Operator created.
    Grant succeeded.
    Grant succeeded.
    Synonym created.
    Synonym created.
    Operator created.
    Operator created.
    Operator created.
    Grant succeeded.
    Synonym created.
    Grant succeeded.
    Synonym created.
    Grant succeeded.
    Synonym created.
    Indextype created.
    Grant succeeded.
    Index created.
    View created.
    No errors.
    Synonym created.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Package created.
    No errors.
    Synonym created.
    Grant succeeded.
    Trigger created.
    No errors.
    Package body created.
    No errors.
    Function created.
    No errors.
    Grant succeeded.
    Synonym created.
    Function created.
    No errors.
    Package body created.
    No errors.
    Package body created.
    No errors.
    Package body created.
    No errors.
    Package body created.
    BEGIN
    ERROR at line 1:
    ORA-04063: package body "XDB.DBMS_XDBZ0" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "XDB.DBMS_XDBZ0"
    ORA-06512: at "XDB.DBMS_XDBZ", line 7
    ORA-06512: at line 2
    declare
    ERROR at line 1:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-04063: package body "XDB.DBMS_XDBUTIL_INT" has errors
    ORA-06512: at "XDB.XDB$PATCHUPSCHEMA", line 98
    ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 3
    ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 14
    ORA-06512: at line 143
    BEGIN
    ERROR at line 1:
    ORA-04063: package body "XDB.DBMS_XDBZ0" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "XDB.DBMS_XDBZ0"
    ORA-06512: at "XDB.DBMS_XDBZ", line 14
    ORA-06512: at line 2
    DECLARE
    ERROR at line 1:
    ORA-31114: XDB configuration has been deleted or is corrupted
    ORA-06512: at "XDB.DBMS_XDB", line 73
    ORA-06512: at line 96
    declare
    ERROR at line 1:
    ORA-01403: no data found
    ORA-06512: at line 5
    Commit complete.
    call xdb.dbms_xdbz0.initXDBSecurity()
    ERROR at line 1:
    ORA-04063: package body "XDB.DBMS_XDBZ0" has errors
    BEGIN
    ERROR at line 1:
    ORA-04063: package body "XDB.DBMS_XDBZ0" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "XDB.DBMS_XDBZ0"
    ORA-06512: at "XDB.DBMS_XDBZ", line 7
    ORA-06512: at line 2
    Commit complete.
    grant all on XDB.XDB$ACL to public
    ERROR at line 1:
    ORA-00942: table or view does not exist
    Commit complete.
    declare
    ERROR at line 1:
    ORA-31000: Resource 'http://xmlns.oracle.com/xdb/acl.xsd' is not an XDB schema
    document
    ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 3
    ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 14
    ORA-06512: at line 63
    declare
    ERROR at line 1:
    ORA-03113: end-of-file on communication channel
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    No errors.
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    No errors.
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    No errors.
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:

    Refer MOS note 243554.1 for reinstallation of XDB.

  • I am new to OWC , installed all the required software's and trying to install OWC sites in weblogic server and in the middle of the installation it is creating all the required tables and throwing below exception

    [2013-06-12 21:52:15,554 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=xceleditor&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=63&PASSWORD=<user password>&
    [2013-06-12 21:52:15,566 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=xceladmin&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=127&PASSWORD=<user password>&
    [2013-06-12 21:52:15,578 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=xcelpublish&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=63&PASSWORD=<user password>&
    [2013-06-12 21:52:15,590 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=Visitor&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=63&PASSWORD=<user password>&
    [2013-06-12 21:52:15,602 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=VisitorAdmin&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=127&PASSWORD=<user password>&
    [2013-06-12 21:52:15,614 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=RemoteClient&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=127&PASSWORD=<user password>&
    [2013-06-12 21:52:15,627 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=WSUser&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=1&PASSWORD=<user password>&
    [2013-06-12 21:52:15,639 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=WSEditor&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=63&PASSWORD=<user password>&
    [2013-06-12 21:52:15,652 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/AddACL?name=WSAdmin&command=addacl&COMMANDNAME=READURL&USERNAME=ContentServer&permission=127&PASSWORD=<user password>&
    [2013-06-12 21:52:15,663 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.EventManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'CSEvents'
    [2013-06-12 21:52:15,664 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xml] Installation Error in Basic/Install: errno -22 from EVENTMANAGER.INSTALL: Error: com.openmarket.xcelerate.commands.EventManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'CSEvents'
    [2013-06-12 21:52:15,666 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURL successful ReadURL for element OpenMarket/Xcelerate/Installation/Basic/Install?editacl=xceleditor&adminacl=xceladmin&COMMANDNAME=READURL&upgrade-log=C:/owcSites/oracle/webcenter/sites/logs/sites.log&USERNAME=ContentServer&upgradefrom=0.0.0.0.0&PASSWORD=<user password>&
    [2013-06-12 21:52:15,681 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.ObjectPublishManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'ObjectPublish'
    [2013-06-12 21:52:15,682 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.DistributionListDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'DistributionList'
    [2013-06-12 21:52:15,682 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.ApprovedAssetsDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'ApprovedAssets'
    [2013-06-12 21:52:15,683 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.AssetExportTargetManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetExportData'
    [2013-06-12 21:52:15,684 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.AssetDefaultTemplateManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetDefaultTemplate'
    [2013-06-12 21:52:15,684 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.AssetPublishListDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetPublishList'
    [2013-06-12 21:52:15,685 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.framework] error: errno -22 on attempt to create table
    [2013-06-12 21:52:15,686 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.SessionTableDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'PubSession'
    [2013-06-12 21:52:15,687 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.PubTargetManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'PubTarget'
    [2013-06-12 21:52:15,688 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.framework] error: errno -22 on attempt to create table
    [2013-06-12 21:52:15,698 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xcelerate] Error: com.openmarket.xcelerate.commands.EmbeddedReferenceTableDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'EmbeddedReference'
    [2013-06-12 21:52:15,699 IST] [INFO ] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.xml] Xcelerate Installation Error in Publish/Install: errno -22 from APPROVEDASSETS.INSTALL: Error: com.openmarket.xcelerate.commands.ApprovedAssetsDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'ApprovedAssets' errno -22 from ASSETTARGETMANAGER.INSTALL: Error: com.openmarket.xcelerate.commands.AssetExportTargetManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetExportData' errno -22 from ASSETTEMPLATEMANAGER.INSTALL: Error: com.openmarket.xcelerate.commands.AssetDefaultTemplateManagerDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetDefaultTemplate' errno -22 from ASSETPUBLISHLIST.INSTALL: Error: com.openmarket.xcelerate.commands.AssetPublishListDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetPublishList' errno -22 from DELIVERYTYPE.INSTALL: Error: com.openmarket.xcelerate.commands.AssetPublishListDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'AssetPublishList' errno -22 from SESSIONMANAGER.INSTALL: Error: com.openmarket.xcelerate.commands.SessionTableDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'PubSession' errno -22 from PUBTARGETMANAGER.INSTALL errno -22 from PUBCONTEXT.INSTALL errno -22 from EMBEDDEDREFERENCETABLE.INSTALL: Error: com.openmarket.xcelerate.commands.EmbeddedReferenceTableDispatcher: Install: com.openmarket.basic.interfaces.AssetException: Error: errno=-22 on call to catalog manager for table 'EmbeddedReference'
    [2013-06-12 21:52:15,699 IST] [ERROR] [.kernel.Default (self-tuning)'] [fatwire.logging.cs.install] READURLProblem in CallElement. Error number=-22
    Can some one help me in identifying the issue.

    Hello,
    errno -22 means " Table already exists."
    This could occur if:
    - The install had failed before during the 2nd stage (i.e. some tables were created previously) and you did not drop the schema before re-install.
    - The database user you are using has access to more than 1 WCS schemas and thought the tables exist already.
    Suggestions:
    1. Make sure the db user is set up as per the Configuring Supporting Software document ( http://docs.oracle.com/cd/E29495_01/doc.1111/webcenter_sites_11gr1_bp1_configuring_supporting_software.pdf )
    2. If the second stage of the install fails, you must drop the database tables, undeploy the WebCenter Sites application, delete the WebCenter Sites file structure, and re-install WebCenter Sites. ( http://docs.oracle.com/cd/E29495_01/doc.1111/webcenter_sites_11gr1_bp1_install_on_weblogic.pdf )
    Regards,
    Yu-Chun

  • Modifying JSP in OAS installation

    .I am auto generating user id and password field and I need to hide these two field from user creation page.I modified JSP in OAS installation.I followed the following steps for doing
    this.
    1.Unpacked xlWebApp.war.
    2.Modified tiles/util/tjspGenerateCreateUserForm.jsp and packed the war file
    again.
    3.Placed the war file in /webapp folder.
    4.started patch_oc4j.cmd (oc4jadmin password) (database password).
    5.Build was successful.
    6.I checked exploded file in
    E:\oracle\oas\j2ee\home\applications\Xellerate\xlWebApp/tiles/util/tjspGenerateC
    reateUserForm.jsp.
    and I can see my modification there.
    7.I tried to access user creation page but it is still showing my old jsp with no
    modification.
    Please tell me what I am missing.I know for Jboss I need to comment out web.xml but I do not see jsp related section in above exploded web.xml .
    installation.
    Regards
    Nitesh

    Hi
    I am having exactly the same problem here but could not make it work even with cleaning precompiled folder before running the patch.
    What i did :
    1. Unpacked xlWebApp.war.
    2. Modified tiles/tjspViewUserDetailsTiles.jsp and packed the war file
    again.
    3. Placed the war file in /webapp folder.
    4. Stopped OIM services with "opmnctl shutdown"
    5. Placed war file into $APPSERVER/j2ee/home/applications/Xellerate
    6. DELETED EVERYTHING INSIDE "$XELLERATE_HOME/xellerate/webapp/precompiled" FOLDER.
    7. Started OIM services "opmnctl startall"
    8. I can see my modified jsp at $APPSERVER/j2ee/home/applications/Xellerate/xlWebApp/tiles/
    9. I started patch_oc4j.sh. Ended successfully.
    10. Now I can see my modified jsp file in $XELLERATE_HOME/xellerate/webapp/precompiled/jsp-temp/tiles folder also.
    11.I tried to access the page but it is still showing my old jsp with no modification.
    What in the name of god am I doing wrong???

  • [svn:bz-trunk] 15533: Back out some local changes to tomcat-users. xml and tomcat-users.xml. install I inadvertently checked in when upgrading ActiveMQ on BlazeDS/trunk .

    Revision: 15533
    Revision: 15533
    Author:   [email protected]
    Date:     2010-04-17 04:20:11 -0700 (Sat, 17 Apr 2010)
    Log Message:
    Back out some local changes to tomcat-users.xml and tomcat-users.xml.install I inadvertently checked in when upgrading ActiveMQ on BlazeDS/trunk.
    Modified Paths:
        blazeds/trunk/servers/apache-tomcat-6.0.14/conf/tomcat-users.xml
        blazeds/trunk/servers/apache-tomcat-6.0.14/conf/tomcat-users.xml.install

    i will not read all that!!!! Format it! Lots of useless information commented.
    java.net.SocketException: java.net.ConnectException: Connection timed out: connect
    at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)
    Tells me you have a connection error on Mysql. Quick search show me this:
    <Resource name="jdbc/passport" auth="Container"
    type="javax.sql.DataSource" driverClassName="com.mysql.jdbc.Driver"
    url="jdbc:mysql://258.1.54.134:3306/xmnext_passport"
    username="dda" password="zhoussda" maxActive="20" maxIdle="10"
    maxWait="-1"/>
    Can you connect to the server using thos setting with a mysql client in the server?

  • Regarding OCMS installation and verification by using Oracle Communicator

    Hi all,
    I am new to this installation.
    I am installed OCMS in windowsXP and TimesTen as database.
    While Instaling the OCMS I created 4 test users with test.user as prefix.
    Now i am trying to connect to oracle communicator using the username and password created at the time of OCMS installation but i am not able to login into that.
    Please help me to solve this.
    I am giving some installation details below.
    Thanks in advance.
    Details:
    The following are the configuration details you selected during installation of the Oracle Communication and Mobility Server: ( these details are also stored in XML format at D:\product\10.1.3.3\ocms_1\sdp\install\installconfig.xml )
    Installation Directory: D:\product\10.1.3.3\ocms_1
    Installation Type: typical
    Installation Mode: Install standalone developer mode (does not require existing AS)
    Locale: en(English)
    OC4J HTTP Port: 8888
    Installed Components and their Configuration
    SIP Container
    SIP Port: 5060
    SIP Domain: sdc6.corp.siebel.com
    SIP Realm: sdc6.corp.siebel.com
    Subscriber Data Services
    TimesTen Home: D:\TimesTen\tt70
    Number of Test Users: 4
    Test Username Prefix: test.user
    Proxy Registrar
    Presence
    Presence Port: 5071
    Application Router

    I think you are likely to get more response via the OCMS forum here
    Communications Converged Application Server
    Chris

  • Error:--Can anyone help me...........

    Hi All,
    I am getting following error while installing following .sar filesof e-Gate:- MFS,SunJavaSystemeWay,SybaseeWay,MQSerieseWay and eIndex
    Error is:--
    Install Directory File Name is: C:\JavaCAPS51\repository\upload\C49D9F4CBEF0B0AE5E697633F3680975\gsr76487\install.xml
    Installation Started, Please wait ...
    Refer to this upload session's Logs at:
    C:\JavaCAPS51\repository\server\logs\eManagerInstaller-1157359911268.log
    1 :
    2 : install:
    3 : [InstallRepAPI] API class name: com.stc.mfs.repository.impl.MfsManagerImpl
    4 : [InstallRepAPI] Connecting to Repository: http://axa-foe649:12000/Hexrepo
    5 : [InstallRepAPI] API SYSTEM ID: MfsManager/SBYN0001
    6 : [InstallRepAPI] Adding JAR files for API: [C:\JavaCAPS51\repository\upload\C49D9F4CBEF0B0AE5E697633F3680975\gsr76487\lib\mfsrepository.jar, C:\JavaCAPS51\repository\upload\C49D9F4CBEF0B0AE5E697633F3680975\gsr76487\lib\mfsbpi.jar]
    7 :
    8 : BUILD FAILED
    9 : file:C:/JavaCAPS51/repository/upload/C49D9F4CBEF0B0AE5E697633F3680975/gsr76487/install.xml:20: com.stc.repository.RepositoryException:
    10 : Could not get information for an object with OID Hexrepo of type {01000000-23A61B690D0100-0A012E8C-01}
    11 :
    12 : No server error detail
    13 :
    14 : Total time: 40 seconds
    Reported execute exit value: 1
    Buildfile: C:\JavaCAPS51\repository\upload\C49D9F4CBEF0B0AE5E697633F3680975\gsr76487\install.xml
    Executing installation script failed.
    Failed to execute ant:
    Executing installation script failed.
    Adding product MFS to the Failed List.
    Executing installation script failed.

    Try examining the temp directory on your box. I haven't done an Win install for CAPS but have done a few Solaris installs and have come across an eway or 2 that doesn't get cleaned out of the tmp directory after another user's install. So when I go to upload the same component for a different instance of CAPS it then chokes (though I don't recall seeing the specific exception you detail). Directory I had to remove on Solaris (or Unix) is /var/tmp/XSDManager (find Win equivalant). I found that by removing the XSDManager directory that my problem was resolved and could continue the component upload (though the XSDManager would again need to be removed afterwards or the next person doing install of same component for different CAPS instance would run into same snag). The problem may not be the XSDManager in your case but still may be a leftover directory in your tmp directory that didn't get cleaned up by a previous install of those components. If this is the first and only instance of CAPS that you are installing on that box then this info is of little help.

  • WorldPay Integration

    Has anybody integrated the WorldPay third party payment servlets within
              WebLogic 5.1?
              The problem I have is the WorldPay properties file (select.properties)
              is not being read. I'm pretty sure it's a classpath problem.
              Any thoughts?
              Please ignore message posted by Rob Gregson
              

    Update on how to install WorldPay seamless payment gateway on a BC site.
    I had a lot of trouble installing this gateway but, thanks to some very patient and helpful people, I managed to get it working so wanted to share with everyone how to do it so I can hopefully save others from all the headaches this process has caused me!
    The first thing to note is that a standard Installation ID from WorldPay will not work with BC. You need to apply for an Invisible XML installation.
    Once you have this, you need to log into your Business Manager Dashboard using your WorldPay account details. Under the 'Setup' tab, you will see your invisible XML password.
    Under 'configuration details' you need to set the Capture Delay to 0 (this means authorise and capture at sale).
    In BC: Installation ID = Invisible XML ID; Password = Invisible XML password.
    Enter these details under the Live WorldPay Gateway - NOT the WorldPay Test Gateway. The credentials they give you do not seem to work on the test gateway.
    In order to test your setup, you will need to contact WorldPay support and convince them to make your account live for 1 test transaction.
    If you are trying to process a transaction and you get the following error: PMII.badPayMethodAndAcqAmount it either means that your Payment Capture Settings (Capture Delay) are not set to 0, or that the account has not been switched out of test mode on WorldPay's end.
    A huge thanks to Matt Baracz and the BC support team for helping me get this sorted out

  • Problem when install CAPS

    Hi guys, I need help :-)
    I managed to download the egate package of the sun enterprise system, however during the uploading of the egate package (egate.sar) I am getting a failed error.
    eGate (1 of 1 Product List)
    Bottom of Form
    Product Name : eGate
    Product Version : 5.1.0
    Installed by User : Administrator
    SAR File Name : C:\JavaCAPS51\repository\upload\1913110EA9DFFA68B2EBF359BF4C9EFE\gsr2285.sar
    From Directory : C:\JavaCAPS51\repository\upload\1913110EA9DFFA68B2EBF359BF4C9EFE\gsr2285
    File [0] = BaseESR.sar
    File [1] = basicmapper.sar
    File [2] = cme.sar
    File [3] = codegenframework.sar
    File [4] = codegenvalidation.sar
    File [5] = commonmodel.sar
    File [6] = commons.jxpath.sar
    File [7] = configeditor.sar
    File [8] = DatabaseModel.sar
    File [9] = deploycli.sar
    File [10] = deploymenteditor.sar
    File [11] = edesigner.sar
    File [12] = edhelp.sar
    File [13] = eInsightIntegration.sar
    File [14] = EncodingConverter.sar
    File [15] = eventmanagement.sar
    File [16] = eWaysCommon.sar
    File [17] = guirepmanager.sar
    File [18] = install.xml
    File [19] = javadebugger.sar
    File [20] = javaEditorModel.sar
    File [21] = jce.sar
    File [22] = jcealerter.sar
    File [23] = jcecodegen.sar
    File [24] = jmscodegen.sar
    File [25] = jmsjca.sar
    File [26] = login.sar
    File [27] = META-INF
    File [28] = mqjmsmessageserver.sar
    File [29] = nb-cookies.sar
    File [30] = nodefilechooser.sar
    File [31] = otdcodegen.sar
    File [32] = otdcsvwizard.sar
    File [33] = otdfcxwizard.sar
    File [34] = otdtester.sar
    File [35] = otdud1flatwizard.sar
    File [36] = otdud1wizard.sar
    File [37] = projectexplorer.sar
    File [38] = queue.sar
    File [39] = repofiler.sar
    File [40] = reportGenerator.sar
    File [41] = RuntimeServer.sar
    File [42] = schedulerotd.sar
    File [43] = smeks.sar
    File [44] = stcacl.sar
    File [45] = stcconfigurationmodule.sar
    File [46] = stccustomotdeditormodule.sar
    File [47] = stccustomotdwizardcommonmodule.sar
    File [48] = stcdeploymentframeworkmodule.sar
    File [49] = stcdtdwizardmodule.sar
    File [50] = stcenvironmentexplorer.sar
    File [51] = stcimpactanalysis.sar
    File [52] = stcimportexport.sar
    File [53] = stcintegserver.sar
    File [54] = stcjmsotdmodule.sar
    File [55] = stclicense.sar
    File [56] = stclog4JAdapter.sar
    File [57] = stclogicalhost.sar
    File [58] = stcmessageserver.sar
    File [59] = stcnaming.sar
    File [60] = stcotdeditormodule.sar
    File [61] = stcotdlaunchermodule.sar
    File [62] = stcotdmodule.sar
    File [63] = stcrepositoryclient.sar
    File [64] = stcversioncontrol.sar
    File [65] = stcwizardcommonmodule.sar
    File [66] = stcxsdwizardmodule.sar
    File [67] = sunJavaSystem81.sar
    File [68] = sunJavaSystem81EmbeddedMessageServer.sar
    File [69] = topic.sar
    File [70] = variableConstants.sar
    File [71] = viewmanager.sar
    File [72] = webservices.sar
    File [73] = wsdlcodegen.sar
    File [74] = wsdleditor.sar
    File [75] = wsdlotd.sar
    File [76] = xce.sar
    File [77] = xcecodegen.sar
    File [78] = xsdcodegen.sar
    File [79] = xsdeditor.sar
    Hot Deployment URL is: http://localhost:12000/manager
    Install Directory File Name is: C:\JavaCAPS51\repository\upload\1913110EA9DFFA68B2EBF359BF4C9EFE\gsr2285\install.xml
    Installation Started, Please wait ...
    Refer to this upload session's Logs at:
    C:\JavaCAPS51\repository\server\logs\eManagerInstaller-1170198173231.log
    1 :
    2 : install:
    3 : [installsar] ***************************************************************
    4 : [installsar] Installing SAR: commonmodel.sar
    5 : [installsar] Executing script: C:\JavaCAPS51\repository\work\1170198181638/install.xml
    6 : [unjar] Expanding: C:\JavaCAPS51\repository\upload\1913110EA9DFFA68B2EBF359BF4C9EFE\gsr2285\commonmodel.sar into C:\JavaCAPS51\repository\work\1170198181638
    7 :
    8 : all:
    9 : [InstallRepAPI] API class name: com.stc.model.common.externalsystem.impl.ExternalSystemManagerImpl
    10 : [InstallRepAPI] Connecting to Repository: http://localhost:12000/RepositoryName
    11 : [InstallRepAPI] API SYSTEM ID: CommonExternalSystemManager/SBYN5454
    12 : [InstallRepAPI] Updating JAR files for API: [C:\JavaCAPS51\repository\work\1170198181638\lib\com.stc.commonmodelapi.jar, C:\JavaCAPS51\repository\work\1170198181638\lib\com.stc.commonmodelimpl.jar]
    13 : [InstallRepAPI] API installed successfully.
    14 : [InstallRepAPI] API class name: com.stc.model.common.impl.ModuleManagerImpl
    15 : [InstallRepAPI] Connecting to Repository: http://localhost:12000/RepositoryName
    16 : [InstallRepAPI] API SYSTEM ID: ModuleManager/SBYN900
    17 : [InstallRepAPI] Updating JAR files for API: [C:\JavaCAPS51\repository\work\1170198181638\lib\com.stc.commonmodelapi.jar, C:\JavaCAPS51\repository\work\1170198181638\lib\com.stc.commonmodelimpl.jar]
    18 : [InstallRepAPI] API installed successfully.
    19 : [InstallRepAPI] API class name: com.stc.model.common.impl.ProjectManagerImpl
    20 : [InstallRepAPI] Connecting to Repository: http://localhost:12000/RepositoryName
    21 : [InstallRepAPI] API SYSTEM ID: ProjectManager/SBYN700
    22 : [InstallRepAPI] Updating JAR files for API: [C:\JavaCAPS51\repository\work\1170198181638\lib\com.stc.commonmodelapi.jar, C:\JavaCAPS51\repository\work\1170198181638\lib\com.stc.commonmodelimpl.jar]
    23 : [InstallRepAPI] API installed successfully.
    24 : [InstallRepAPI] API class name: com.stc.model.common.impl.EnvironmentManagerImpl
    25 : [InstallRepAPI] Connecting to Repository: http://localhost:12000/RepositoryName
    26 : [InstallRepAPI] API SYSTEM ID: EnvironmentManager/SBYN701
    27 : [InstallRepAPI] Updating JAR files for API: [C:\JavaCAPS51\repository\work\1170198181638\lib\com.stc.commonmodelapi.jar, C:\JavaCAPS51\repository\work\1170198181638\lib\com.stc.commonmodelimpl.jar]
    28 : [InstallRepAPI] API installed successfully.
    29 : [InstallModule] Module: commonmodel
    30 : [InstallModule] Repository directory: InstallManager/edesigner/modules/
    31 : [InstallModule] ED directory: modules/
    32 : [InstallModule] Distributed URL: http://localhost:12000/repository/RepositoryName
    33 : [InstallModule] Connecting to Repository: http://localhost:12000/RepositoryName
    34 : [InstallModule] Updating Module: commonmodel
    35 : [InstallModule] local temp catalog.xml path : C:\JavaCAPS51\repository\work\1170198181638\_tmpcatalog.xml
    36 : [InstallModule] retrieving catalog.xml from repository
    37 : [InstallModule] Adding Module: commonmodel
    38 : [InstallModule] ED Module installed successfully.
    39 : [InstallJava] Connecting to Repository: http://localhost:12000/RepositoryName
    40 : [InstallJava] Filename : C:\JavaCAPS51\repository\work\1170198181638\commonmodel.nbm
    41 : [InstallJava] Adding/Updating Java Module: commonmodel
    42 : [InstallJava] Java Module installed successfully.
    43 : [installsar] SAR file: commonmodel.sar installed successfully.
    44 : [installsar] ***************************************************************
    45 : [installsar] ***************************************************************
    46 : [installsar] Installing SAR: commons.jxpath.sar
    47 : [installsar] Executing script: C:\JavaCAPS51\repository\work\1170198187341/install.xml
    48 : [unjar] Expanding: C:\JavaCAPS51\repository\upload\1913110EA9DFFA68B2EBF359BF4C9EFE\gsr2285\commons.jxpath.sar into C:\JavaCAPS51\repository\work\1170198187341
    49 :
    50 : all:
    51 : [InstallModule] Module: commonsJXPath
    52 : [InstallModule] Repository directory: InstallManager/edesigner/modules/
    53 : [InstallModule] ED directory: modules/
    54 : [InstallModule] Distributed URL: http://localhost:12000/repository/RepositoryName
    55 : [InstallModule] Connecting to Repository: http://localhost:12000/RepositoryName
    56 : [InstallModule] Adding Module: commonsJXPath
    57 : [InstallModule] local temp catalog.xml path : C:\JavaCAPS51\repository\work\1170198187341\_tmpcatalog.xml
    58 : [InstallModule] retrieving catalog.xml from repository
    59 : [InstallModule] created Module from NBM file : C:\JavaCAPS51\repository\work\1170198187341\modules\commons.jxpath.nbm
    60 : [InstallModule] module doesn't exist, adding to catalog.xml
    61 : [InstallModule] wrote temp catalog.xml
    62 : [InstallModule] uploaded temp catalog.xml to repository
    63 : [InstallModule] ED Module installed successfully.
    64 : [InstallJava] Connecting to Repository: http://localhost:12000/RepositoryName
    65 : [InstallJava] Filename : C:\JavaCAPS51\repository\work\1170198187341\modules\commons.jxpath.nbm
    66 : [InstallJava] Adding/Updating Java Module: commonsJXPath
    67 : [InstallJava] Java Module installed successfully.
    68 : [installsar] SAR file: commons.jxpath.sar installed successfully.
    69 : [installsar] ***************************************************************
    70 : [installsar] ***************************************************************
    71 : [installsar] Installing SAR: stcrepositoryclient.sar
    72 : [installsar] Executing script: C:\JavaCAPS51\repository\work\1170198188997/install.xml
    73 : [unjar] Expanding: C:\JavaCAPS51\repository\upload\1913110EA9DFFA68B2EBF359BF4C9EFE\gsr2285\stcrepositoryclient.sar into C:\JavaCAPS51\repository\work\1170198188997
    74 :
    75 : install:
    76 : [InstallModule] Module: RepositoryClient
    77 : [InstallModule] Repository directory: InstallManager/edesigner/modules/
    78 : [InstallModule] ED directory: modules/
    79 : [InstallModule] Distributed URL: http://localhost:12000/repository/RepositoryName
    80 : [InstallModule] Connecting to Repository: http://localhost:12000/RepositoryName
    81 : [InstallModule] Adding Module: RepositoryClient
    82 : [InstallModule] local temp catalog.xml path : C:\JavaCAPS51\repository\work\1170198188997\_tmpcatalog.xml
    83 : [InstallModule] retrieving catalog.xml from repository
    84 : [InstallModule] created Module from NBM file : C:\JavaCAPS51\repository\work\1170198188997\com.stc.repositoryclient.nbm
    85 : [InstallModule] module doesn't exist, adding to catalog.xml
    86 : [InstallModule] wrote temp catalog.xml
    87 : [InstallModule] uploaded temp catalog.xml to repository
    88 : [InstallModule] ED Module installed successfully.
    89 : [InstallJava] Connecting to Repository: http://localhost:12000/RepositoryName
    90 : [InstallJava] Filename : C:\JavaCAPS51\repository\work\1170198188997\com.stc.repositoryclient.nbm
    91 : [InstallJava] Adding/Updating Java Module: RepositoryClient
    92 : [InstallJava] Java Module installed successfully.
    93 : [installsar] SAR file: stcrepositoryclient.sar installed successfully.
    94 : [installsar] ***************************************************************
    95 : [installsar] ***************************************************************
    96 : [installsar] Installing SAR: viewmanager.sar
    97 : [installsar] Executing script: C:\JavaCAPS51\repository\work\1170198191138/install.xml
    98 : [unjar] Expanding: C:\JavaCAPS51\repository\upload\1913110EA9DFFA68B2EBF359BF4C9EFE\gsr2285\viewmanager.sar into C:\JavaCAPS51\repository\work\1170198191138
    99 :
    100 : all:
    101 : [InstallModule] Module: viewmanager
    102 : [InstallModule] Repository directory: InstallManager/edesigner/modules/
    103 : [InstallModule] ED directory: modules/
    104 : [InstallModule] Distributed URL: http://localhost:12000/repository/RepositoryName
    105 : [InstallModule] Connecting to Repository: http://localhost:12000/RepositoryName
    106 : [InstallModule] Adding Module: viewmanager
    107 : [InstallModule] local temp catalog.xml path : C:\JavaCAPS51\repository\work\1170198191138\_tmpcatalog.xml
    108 : [InstallModule] retrieving catalog.xml from repository
    109 : [InstallModule] created Module from NBM file : C:\JavaCAPS51\repository\work\1170198191138\modules\viewmanager.nbm
    110 : [InstallModule] module doesn't exist, adding to catalog.xml
    111 : [InstallModule] wrote temp catalog.xml
    112 : [InstallModule] uploaded temp catalog.xml to repository
    113 : [InstallModule] ED Module installed successfully.
    114 : [InstallJava] Connecting to Repository: http://localhost:12000/RepositoryName
    115 : [InstallJava] Filename : C:\JavaCAPS51\repository\work\1170198191138\modules\viewmanager.nbm
    116 : [InstallJava] Adding/Updating Java Module: viewmanager
    117 : [InstallJava] Java Module installed successfully.
    118 : [installsar] SAR file: viewmanager.sar installed successfully.
    119 : [installsar] ***************************************************************
    120 : [installsar] ***************************************************************
    121 : [installsar] Installing SAR: cme.sar
    122 : [installsar] Executing script: C:\JavaCAPS51\repository\work\1170198192528/install.xml
    123 : [unjar] Expanding: C:\JavaCAPS51\repository\upload\1913110EA9DFFA68B2EBF359BF4C9EFE\gsr2285\cme.sar into C:\JavaCAPS51\repository\work\1170198192528
    124 :
    125 : all:
    126 : [InstallRepAPI] API class name: com.stc.cme.migration.CMEManagerImpl
    127 : [InstallRepAPI] Connecting to Repository: http://localhost:12000/RepositoryName
    128 : [InstallRepAPI] API SYSTEM ID: CMEManager/SBYN110
    129 : [InstallRepAPI] Adding JAR files for API: [C:\JavaCAPS51\repository\work\1170198192528\lib\com.stc.commonmodelapi.jar, C:\JavaCAPS51\repository\work\1170198192528\lib\com.stc.commonmodelimpl.jar, C:\JavaCAPS51\repository\work\1170198192528\lib\com.stc.cmemodelapi.jar, C:\JavaCAPS51\repository\work\1170198192528\lib\com.stc.cme.jar, C:\JavaCAPS51\repository\work\1170198192528\lib\JGo.jar, C:\JavaCAPS51\repository\work\1170198192528\lib\JGoLayout.jar, C:\JavaCAPS51\repository\work\1170198192528\lib\JGoSVG.jar, C:\JavaCAPS51\repository\work\1170198192528\lib\log4j.jar, C:\JavaCAPS51\repository\work\1170198192528\lib\concurrent.jar, C:\JavaCAPS51\repository\work\1170198192528\lib\com.stc.edutilapi.jar]
    130 : [InstallRepAPI] API installed successfully.
    131 : [InstallModule] Module: CME
    132 : [InstallModule] Repository directory: InstallManager/edesigner/modules/
    133 : [InstallModule] ED directory: modules/
    134 : [InstallModule] Distributed URL: http://localhost:12000/repository/RepositoryName
    135 : [InstallModule] Connecting to Repository: http://localhost:12000/RepositoryName
    136 : [InstallModule] Adding Module: CME
    137 : [InstallModule] local temp catalog.xml path : C:\JavaCAPS51\repository\work\1170198192528\_tmpcatalog.xml
    138 : [InstallModule] retrieving catalog.xml from repository
    139 : [InstallModule] Error while reading the Catalog.xml com.stc.repository.RepositoryException: Copy file failed. from : C:/JavaCAPS51/repository/data/files/InstallManager/catalog.xml to : C:/JavaCAPS51/repository/work/1170198192528/_tmpcatalog.xml : rename failed. : Cannot rename file: C:\JavaCAPS51\repository\work\1170198192528\forCopy50334.tmp to C:\JavaCAPS51\repository\work\1170198192528\_tmpcatalog.xml
    140 : [InstallModule] Cannot rename file: C:\JavaCAPS51\repository\work\1170198192528\forCopy50334.tmp to C:\JavaCAPS51\repository\work\1170198192528\_tmpcatalog.xml
    141 : [InstallModule]
    142 : [InstallModule] No server error detail
    143 :
    144 : BUILD FAILED
    145 : file:C:/JavaCAPS51/repository/work/1170198192528/install.xml:21: Copy file failed. from : C:/JavaCAPS51/repository/data/files/InstallManager/catalog.xml to : C:/JavaCAPS51/repository/work/1170198192528/_tmpcatalog.xml : rename failed. : Cannot rename file: C:\JavaCAPS51\repository\work\1170198192528\forCopy50334.tmp to C:\JavaCAPS51\repository\work\1170198192528\_tmpcatalog.xml
    146 : Cannot rename file: C:\JavaCAPS51\repository\work\1170198192528\forCopy50334.tmp to C:\JavaCAPS51\repository\work\1170198192528\_tmpcatalog.xml
    147 :
    148 : Total time: 18 seconds
    Reported execute exit value: 1
    Buildfile: C:\JavaCAPS51\repository\upload\1913110EA9DFFA68B2EBF359BF4C9EFE\gsr2285\install.xml
    Executing installation script failed.
    Failed to execute ant:
    Executing installation script failed.
    Adding product eGate to the Failed List.
    Executing installation script failed.
    ::::::::::::::::: Installation Failed for :::::::::::::::::::::::::::::::
    Name: eGate Version: 5.1.0
    Deleting File: C:\JavaCAPS51\repository\upload\1913110EA9DFFA68B2EBF359BF4C9EFE\gsr2285.sar
    Deleting Folder: C:\JavaCAPS51\repository\upload\1913110EA9DFFA68B2EBF359BF4C9EFE\gsr2285

    From the following looks like renaming problem
    139 : [InstallModule] Error while reading the Catalog.xml com.stc.repository.RepositoryException: Copy file failed. from : C:/JavaCAPS51/repository/data/files/InstallManager/catalog.xml to : C:/JavaCAPS51/repository/work/1170198192528/_tmpcatalog.xml : rename failed. : Cannot rename file: C:\JavaCAPS51\repository\work\1170198192528\forCopy50334.tmp to C:\JavaCAPS51\repository\work\1170198192528\_tmpcatalog.xml
    Thinking loud - before creating the file is it trying to rename?? bcz of clock speed/processor speed..
    bcz today i again i am able 2 install the product sucessfully. not able to reproduce the above bug/problem.
    What is your m/c configuration?
    thanks
    ram

  • Error installing Oracle Counters for Windows Performance Monitor

    Hello,
    I have installed Oracle EE 11g 11.2.0.1.0 on a Windows 2008 R2 server. Now, I am using the Oracle Universal Installer to install the Oracle Counters for Windows Performance Monitor 11.2.0.1.0
    Source path is D:\Share\11gR2_win32_11gR2_database_install\database\stage\products.xml
    Installation Type is Custom
    Install Location is C:\app\dmadmin
    Path is C:\app\dmadmin\OraHome_1
    I de-select all product components and select the following two:
    Oracle Windows Interfaces 11.2.0.1.0
    Oracle Counters for Windows Performance Monitor 11.2.0.1.0
    I get the following error:
    OUI-10150:Error: A runtime exception occurred while setting s_digCfgNamingLabelSIDnull in component Database 11g 11.2.0.1.0 . Installation cannot continue for this component.
    I am given the choice of Stop installation of all products and Stop installation of this component only which both result in non-installation of selected component.
    Does anyone have any advice or solutions for this error? I have tried re-booting the server, but get the same error.
    Thanks for your assistance,
    Stumped

    OUI from ORACLE_HOME (OH\oui\bin\setup.exe) cannot be used to install components from 11.2.0.1 installation media (products.xml)
    This is documented, but I am not able to locate it now.
    Have you checked if the Performance Monitor files are already installed or not?
    Thanks
    Srinivas

  • DB_VERSION_MISMATCH error every day

    Every day when I run my test.pl program for the first time, I see this:
    DbEnv::open: DB_VERSION_MISMATCH: Database environment version mismatch in test.pl,
    line 35
    The docs say that this error means "The version of the Berkeley DB library doesn't match the version that created the database environment". But I haven't changed my BDB XML installation.
    If I delete all the files in my test database directory and reload my test data, everything is fine. I can run my test program again and again all day long. But when I come in next morning, I get the error! This is the code I'm using:
        my $ENVIRONMENT = 'test-env';
        my $ENV_FLAGS   = Db::DB_CREATE | Db::DB_INIT_LOCK | Db::DB_INIT_LOG
                            | Db::DB_INIT_MPOOL | Db::DB_INIT_TXN;
        my $env = new DbEnv;
        x eval { $env->open($ENVIRONMENT, $ENV_FLAGS, 0) };'x' is just a function that traps the exception. Line 35 is the line with the open() call.
    Does anybody know what I'm doing wrong?
    Thanks, Dave

    Could your installation be picking up another version
    — probably preexisting — of the Berkeley DB libs?Good thought. I've done some digging.
    There are two versions of Berkeley DB already installed on my system, according to YaST: 4.3.27-3.1 and 1.85-89. I don't want to interfere with those because I don't know what might be using them. Then there's the version which came with the dbxml I downloaded: 4.3.29, which is presently under /opt/berkeley
    I seem to be picking up 4.3.29. When I run /opt/berkeley/bin/db_verify -V it says "Sleepycat Software: Berkeley DB 4.3.29: (September 6, 2005)". While if I run /usr/bin/db_verify -V it says "Sleepycat Software: Berkeley DB 4.3.27: (June 1, 2005)" but both are supposedly compatible with the current dbxml release, according to the release notes.
    If I run /opt/berkeley/bin/dbxml -h test-env-old (i.e. using yesterday's data) it says
    Program version 4.3 doesn't match environment version
    Error opening environment test-env-old: DbEnv::open:
    DB_VERSION_MISMATCH: Database environment version mismatchbut rather annoyingly doesn't tell me what version it thinks the data is!!!
    dbxml is happy with a new test-env database that I've created today in Perl.
    I haven't found any way to find out what version the data in test-env-old thinks it is. Is there some utility that will do this? I tried looking in the files but didn't spot anything.
    That dbxml behaves the same as my test program seems to eliminate some Perl artefact as the source of this problem but in case it's useful to you or some Sleepycat person, I added a call to DbXml::printVersionInfo() to my test program, which duly reports:
    perl  : 5.008006
    dbxml : Sleepycat Software: Berkeley DB XML 2.2.13: (December 19, 2005)
    db    : Sleepycat Software: Berkeley DB 4.3.29: (September  6, 2005)
    xerces: whateverso it seems to be finding the right db library.
    I've seen that happen elsewhere. Usually it results
    in a library compatibility error though, rather than
    a database version error.Any other ideas? I really appreciate all the help you're giving me.
    This is a minor nuisance while I'm testing, but it's a complete showstopper for using dbxml in production, of course.

  • PeopleSoft XML Publisher Desktop installation issue

    Hi,
    I've tried to install the XML publisher desktop desing helper.
    I've installed it without error. But when i open the Office word program, it didn't show up the Template Builder menu on office tool bar.
    I've tried to do the following:
    1. Set the trust center setting in word option, Marco is all enabled, and the VBA project is checked.
    2. Close the Microsfot program, IE, Word, etc.
    3. Close the MSN Messager program
    4. Uninstall the MSN Live
    5. Then I re-run the installation file of XMLp several times to re-install it.
    After that, i still can not find any menu tool bar named "Templdate Builder" in word program.
    During the installation, there's no error, the install process is smoothly ended, but in the word program there's no menu for Template Builder.
    The version of Microsoft Word is 2007, and the version of XMLp Design helper for Word is 5.6.2, and the Java JRE version is 1.6.07.
    Please help on figuring this!
    Thanks,
    Saxon SI

    Hi:
    Check for Add-Ins in Word Options. Make sure that TemplateBuilder.dot is active; and look for 'Add-Ins' menu on your document. XML Publisher menus will be visible on that tab.
    Thanks and Regards,
    Sameer.

  • XML Publisher Enterprise Installation

    I installed Xml Publisher Enterprise version 5.6.2 to our test PC with its own oracle home as c:\ora_xmlp. The installation ran successfully. But when I ran xmlpserverstart.bat, it stopped at the line: "Oracle containers for J2EE log (10.1.3.0) initialized..." and didn't go on. Should I use the same path as oracle database or application server?
    Please help, Thanks.
    - Jessie

    Hi Jessie.
    That's what it's supposed to do. That message means the OC4J engine started properly. Now you can access the application by going to:
    http://localhost:15101/xmlpserver
    unless you changed anything in the install (which I'm assuming from the formulation of your note is nothing).
    Cheers,
    Dave

Maybe you are looking for

  • Samsung LCD TV  "Format not supported" error message?

    I have been using my Samsung LCD TV Model number LC320SS9-A for years via a HMDI cable.   As of a couple of weeks ago I now get the follow error message,  "Format not supported" on the TV.  Running 10.8.2   2.3 GHz Intel Core i5 with 4GB DDR3 memory.

  • White Screen in menu and simulator

    I'm running into a problem of DVD Studio Pro displaying a white menu screen when the program opens. I need to toggle between the different screen displays in order to see any file that I assign as the background whether it be video or a still. My sti

  • Oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-271

    Hi All, For the following VO query , select meas_elem_weight from xxg2c_quota_weights_v where org_id = :0 and quota_id = :1 and comp_plan_id =:2 union select 0 meas_elem_weight from dual where not exists (select meas_elem_weight from xxg2c_quota_weig

  • Select Statement Takes 5 Days in Job Queue Manager

    Here's our problem... In one of our packages, there is a D-SQL select statement. Every time we schedule to run that package using job queque manager, it gets stuck. The SQL Tracing shows it's scanning the blocks, but it just won't finish. If we run t

  • Enable Field on current record

    Hi i have multi data block filed. and checkbox field which based on control block My task is when i check checkbox only one field should enabled and my mouse goes to that field e.g item11 item21 item31 chkbox1 item12 item22 item32 chkbox2 Scenario li