Axion RDBMS problem

Hi all,
I m working with the Axion RDBMS ,
I have a problem with the insertion of new records in the tables of my database, the selection is working properly but the insertion seems to be as it is in the transient mode not in the persistent one
Here is the code
class DatabaseConnection {
Statement stmt;
Connection con;
DatabaseConnection(){
try {
Class.forName("org.axiondb.jdbc.AxionDriver");
catch(ClassNotFoundException e) { e.printStackTrace(); }
try {
con = DriverManager.getConnection("jdbc:axiondb:MyDB:MyDB-DIR");
stmt = con.createStatement();
} catch (SQLException e) {     }
public void executeSql(String sql) {
stmt.execute(sql);
} catch (SQLException e) {           System.out.println(e.getMessage());       }
when I create a new instance of my DatabaseConnection class and I want to execute and insert it works but when I close and restart my application all the modification I did are not present
DatabaseConnection db = new DatabaseConnection();
db.executeSql(�INSERT INTO table (id, name) VALUES(1 ,�aName�)�);
if I make a select before I close my application I can see the record I inserted but after restarting the application it disappear
can any one help me ?
mail : [email protected]

FWIW, I've decided to find out what exactly is an Axion RDBMS and found out that this freebie is still in an infancy stage (haven't really figured out whether it's a relational or just a plain database system) and the strange thing about this DB is that in order to make the changes permanent, you must:
1) commit the changes (even tho autocommit is set to true)
2) shutdown the DB and wait a bit before you close the connection
;o)
V.V.

Similar Messages

  • RDBMS PROBLEM DIAGNOSTIC

    제품 : ORACLE SERVER
    작성날짜 : 1995-02-06
    Subject: Recommended Diagnostic Practices
    The diagnostic procedures outlined here are intended as guidelines
    to dealing with various categories of errors. This is by no means
    an exhaustive list as the nature of the specific error invariably dictates
    the type and amount of diagnostic tracing that is required.
    Based on the information gathered via these guidelines it may be necessary
    to successively obtain further traces, as required by Oracle Development.
    This may be an iterative process.
    1. DATA CORRUPTIONS
    1.1 Description of Category
    This category includes all block format corruptions, invalid index entries,
    and corruptions of meta-data (eg.data dictionary).
    1.2 Example:
    ORA-600 [3339] on System datafile
    1.3 Typical Diagnostic Actions:
    (a) Get trace file(s), if the corruption reported as an internal error.
    (b) For table corruptions, attempt to use index (if available) to extract
    data from uncorrupted blocks.
    (c) Obtain redo dumps corresponding to the time of corruption.
    (d) If there is reason to suspect vendor OS problem, complete H/W
    diagnostics need to be carried out.
    (e) Where appropriate, determine if generic or port-specific issue.
    2. LOGICAL CORRUPTIONS
    2.1 Description of Category
    This category refers to cases where the data stored or retrieved by
    a query is incorrect although it isn't necessary that an error is returned
    externally.
    It also includes data dictionary inconsistencies without any detectable block corruption.
    2.2 Example:
    Query returns different results with CBO vs. Rule-based
    2.3 Typical Diagnostic Actions:
    (a) Obtain a reproducible test case or dial-in information.
    (b) Record any visible error messages, get trace files.
    (c) Where appropriate, determine if generic or port-specific issue.
    3. SYSTEM HANGS
    3.1 Description of Category
    This category includes the cases where:
    (i) the database hangs on open after media or instance recovery,
    (ii) the system hangs with users unable to logon or execute operations.
    3.2 Example:
    Database spinning in transaction recovery, on attempting to open.
    3.3 Typical Diagnostic Actions:
    (a) Stack and process state dumps of all Oracle processes, including hung
    processes using the ORADBX utility.
    (b) Obtain complete ALERT.log to establish history of events leading to hang.
    (c) In the case of a hang on database open:
    (i) Set events to determine which stage of recovery is stuck.
    (ii) Dumps of the controlfile, datafile headers, logfile headers, buffers, enqueues and latches.
    (iii) Situation-specific dumps of archive/online logfiles.
    (d) In the case of a system hang, take multiple systemstate dumps at
    intervals.
    (e) Monitor CPU and I/O activity during the hang using o/s utilities.
    (f) Obtain a reproducible test case or dial-in information for development.
    4. PERFORMANCE PROBLEMS
    4.1 Description of Category
    This category comprises (i) General cases of deteriorations in response time
    or batch completion times (ii) performance degradtion on increase in concurrent activity.
    4.2 Example
    System hangs if more than 96 concurrent users.
    4.3 Typical Diagnostic Actions:
    (a) Document performance degradation in terms of specific indicators (response
    time, batch completion time, number of concurrent logins supported,
    efficiency of shared pool management).
    (b) Provide a reproducible test case where possible, or document in detail
    the environment and factors leading to poor performance (for example,
    in the cases where reproducibility depends on concurrency in a production
    environment, document circumstances surrounding degradation like #logins,
    average memory usage, typical functionality invoked, IO activity,
    dynamic statistics on Oracle activity.)
    (c) Where appropriate, determine if generic or port-specific issue.
    (d) If not reproducible in-house, but reproducible with reasonable
    frequency on customer site provide dial-in information for development.
    5. SYSTEM CRASHES
    5.1 Description of Category
    This includes all cases where the database crashes, possibly due to
    one of the background processes dying.
    5.2 Example:
    DBWR crashes periodically during heavy activity
    5.3 Typical Diagnostic Actions:
    (a) Request trace files, ALERT.log and information on circumstances
    surrounding the crash.
    (b) Construct reproducible test case where possible.
    (c) Where relevant, determine if generic or port-specific issue.
    6. CRITICAL FUNCTIONALITY NOT AVAILABLE
    6.1 Description of Category
    This refers to all situations where functionality or vital features relied
    on by a production application becomes unavailable, typically because
    of a bug in the feature. This includes cases where Oracle utilities core dump,
    applications error out due to bugs and recovery is stuck.
    6.2 Example:
    ORA-600[3020] during media recovery application of archive log
    6.3 Typical Diagnostic Actions:
    (a) Where an error is reported, get any trace files produced and relevant
    redo log dumps if necessary. Document completely the circumstances
    leading up to the error.
    (b) Provide a reproducible test case or dial-in information to development.
    (d) Where relevant, determine if generic or port-specific issue.
    7. MEMORY CORRUPTIONS
    7.1 Description of Category
    This includes internal errors signalling memory leaks, corruptions of memory
    data strutures and cache corruptions.
    7.2 Example:
    ORA-600[17271][INSTANTION SPACE LEAK] during pl/sql execution
    7.3 Typical Diagnostic Actions:
    (a) Request trace files when error causes a trace file to be produced.
    (b) Provide reproducible test case where possible; else document circumstances
    of error including (i) Details of OCI or Oracle tool, utility or pre-compiler
    used in application (ii) OS tools or third-party tools used in conjunction
    with the application (iii) Triggers fired by application
    (iv) Packages or procedures executed.

    It is most likely the panel, since your machine has integrated graphics. If you haven't done this kind of repair, replacing the panel out of the lid can be difficult. It can be done if you are careful. Here is the manual:
    http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/e520_e525_hmm_en_0a60536_05.pdf
    If you want to replace the entire lid assembly, it might be easier. I actually have one from an E520 in stock. (It looks like it has a built-in webcam.) Since I don't work on many of this model, I can give you a good price. Send me a pm if interested.

  • Error Headstart in combination Designer 6, Developer 6 HELP

    We have upgraded to Desigener 6.0 and Developer 6.0 (patch 6).
    All the pll's compile when (qmslib50, qmsevh50), the generation of a small application in Designer 6 (was first in Designer 2.1.2) went well.
    When we run the forms we get the following error "FRM-40733 PL/SQL Build in DBMS_ERROR_TEXT failed. I'm searching for two days and haven't come up with a solution
    Please help !?

    You are probably using an Oracle 8.1.5 database an running against Oracle RDBMS problem report 966970. Oracle Support has tested
    it against an 8.1.6 database and there the problem is fixed. There is also a workaround available for 8.1.5, see the Headstart discussion
    forum on OTN and look at the e-mails of Cheryl Riley (thanks Cheryl). I suggest however that you move to 8.1.6.
    Regards,
    Ton

  • OIDCTL

    Hi,
    I have installed ORACLE E.E. 8.1.7.0.0's OID 2.1.1.0.0.
    When I try to initiate the following command:
    oidctl connect=EAIDEMO server=oidldapd instance=1 start
    I get the following error message:
    [gsdsiConnect] ORA-1017, ORA-01017: invalid username/password; logon denied
    I really don't see where I can set up user names or passwords.
    Any hints would be appritiated.
    Thanks

    This is the first time Ive seen this on the 8.1.7 release.
    Are you sure you are using 8.1.7 or 8.1.7.1? Also, what OS
    are you on? Is it Possible that you are using sqlplus or sqlnet
    binaries from 9i on your 8.1.7 instance?
    I found the following bug #1852419 on the oracle bug database.
    Its seems to describe your problem exactly. The only problem is
    that this bug only exists on 9.0 of RDBMS:
    PROBLEM:
    @ unable to change password for a username of type "ab ab"
    @ get ora-1017: invalid username/password; logon denied
    =========================
    DIAGNOSTIC ANALYSIS:
    Here is a very simple testcase to demonstrate the problem:
    SQL> create user "ab ab" identified by d;
    User created.
    @ SQL> password "ab ab";
    @ Changing password for ab ab
    @ New password:
    @ Retype new password:
    ERROR:
    @ ORA-1017: invalid username/password; logon denied
    This problem is fixed in 9.0.2. SQL*Plus no longer strips away the quotation
    @ marks. eg. password "ab ab" is now passed to the database
    server as '"ab ab"' ie. includes the double quotations rather
    than 'ab ab' without the double quotations. Double quotations
    is required for case sensitivity in the database.

  • Unable to view tomcat page..!

    Hi All,
    My OS & DB Details are like that :
    OS: Solaris
    DB : 10.2.0
    As we want to deploy BOP application in PRODUCTION we are trying to open the tomcat page but In test environment we are able to view tomcat page when URL is provided.
    But in production environment we are not able to see tomcat page it is displaying the login page.
    Can anyone help me out

    Vikas Kohli wrote:
    Hi All,
    My OS & DB Details are like that :
    OS: Solaris
    DB : 10.2.0
    As we want to deploy BOP application in PRODUCTION we are trying to open the tomcat page but In test environment we are able to view tomcat page when URL is provided.
    But in production environment we are not able to see tomcat page it is displaying the login page.
    Can anyone help me outso why is this an Oracle RDBMS problem?
    What is the Oracle error number & message that needs to be corrected?

  • For everyone facing unexpected the JBO-25014 error using (ADF) BC

    Hi,
    I think I might have a hint for everyone facing JBO-25014 (Another user has changed the row with primary key oracle.jbo.Key) errors during updates.
    I noticed that during updates, we got unexpected behavior: we have a table with an update row trigger defined on it, where we set values for some columns. During updates via ADF BC (we work with JDev 10.1.3 SU3 and JHeadstart 10.1.3 build 78 against Oracle 8.1.7.4, 9.2.0.7 and 10.2.0.1) we noticed that the value of one of the fields updated via triggers was emptied, although the update could in no way hit the logic for this field. So I reproduced the behavior in the Application Module Tester and also reproduced it in SQL*Plus using a PL/SQL procedure: the problem occurs because of Oracle's RETURNING statement, which is used in ADF BC for fields that need refresh after insert of update. We seem to hit bug 4515623: "Update...RETURNING with a trigger can produce corrupt column data".
    This should be solved in RDBMS 9.2.0.8 (not there yet) and 10.2.0.2 (already released). I still have to test whether 10.2.0.2 does solve our problem, but I thought I would let you know in advance. Maybe someone can test before I can (I have to set up a 10G DB first, since I work with 9.2.0.7),
    Toine van Beckhoven

    Here is additional info on this behavior. I was able to install a 10G DB (10.2.0.1) where I could reproduce the problem. After that I installed patch 10.2.0.2 and tried out it the bug was solved. However: the bug is solved, but not correctly, a new bug is introduced which is still a major problem when you use ADF BC on top of tables with Before Update triggers (but as you can see below, with update triggers containing conditional logic!). So this is really a database problem, but with impact on applications using the refresh after update property in ADF BC! The new bug is known as bug 5115882.
    Here is the script I used to pinpoint the problem (I highlighted the things that really show the problem):
    DROP TABLE test_ts;
    CREATE TABLE test_ts (test_ts_id INTEGER PRIMARY KEY,
    status SMALLINT NOT NULL, someotherfield VARCHAR2(1), edittime DATE);
    CREATE OR REPLACE TRIGGER test_ts_time
    BEFORE UPDATE
    ON test_ts
    REFERENCING OLD AS OLD NEW AS NEW
    FOR EACH ROW
    BEGIN
    -- always update edittime
    :NEW.edittime := SYSDATE;
    -- only update someotherfield conditionally (when status=1)
    IF :NEW.status = 1
    THEN
    :NEW.someotherfield := 'Y';
    END IF;
    END;
    PROMPT Create one row, with status 1 and someotherfield initially 'N'
    INSERT INTO test_ts
    (test_ts_id, status, someotherfield, edittime
    VALUES (1, 1, 'N', SYSDATE
    SELECT test_ts_id, status, someotherfield,
    TO_CHAR (edittime, 'dd-mm-yyyy hh24:mi:ss') edittime
    FROM test_ts;
    SET serverout on
    PROMPT Update the row, with status 2 --> trigger logic will not fire
    DECLARE
    l_someotherfield test_ts.someotherfield%TYPE;
    l_edittime test_ts.edittime%TYPE;
    BEGIN
    FOR i IN 1 .. 100000000
    LOOP
    NULL;
    END LOOP;
    UPDATE test_ts
    SET status = 2
    WHERE test_ts_id = 1
    RETURNING someotherfield, edittime
    INTO l_someotherfield, l_edittime;
    DBMS_OUTPUT.put_line
    ( 'Returned SomeOtherField (should be ''N'' but is empty in 10.2.0.1): '
    || l_someotherfield
    DBMS_OUTPUT.put_line
    ( 'Returned EditTime (should be greater than selected one before): '
    || TO_CHAR (l_edittime, 'dd-mm-yyyy hh24:mi:ss')
    DBMS_OUTPUT.put_line ('-');
    END;
    PROMPT However: someotherfield is really 'N' so why is it returning NULL --> bug
    SELECT test_ts_id, status, someotherfield,
    TO_CHAR (edittime, 'dd-mm-yyyy hh24:mi:ss') edittime
    FROM test_ts;
    PROMPT Update the row, with status 1 --> trigger logic will fire
    DECLARE
    l_someotherfield test_ts.someotherfield%TYPE;
    l_edittime test_ts.edittime%TYPE;
    BEGIN
    FOR i IN 1 .. 100000000
    LOOP
    NULL;
    END LOOP;
    UPDATE test_ts
    SET status = 1
    WHERE test_ts_id = 1
    RETURNING someotherfield, edittime
    INTO l_someotherfield, l_edittime;
    DBMS_OUTPUT.put_line
    ( 'Returned SomeOtherField (should be ''Y'' and is ''Y'' also in 10.2.0.1): '
    || l_someotherfield
    ); DBMS_OUTPUT.put_line
    ( 'Returned EditTime (should be greater than selected one before): '
    || TO_CHAR (l_edittime, 'dd-mm-yyyy hh24:mi:ss')
    DBMS_OUTPUT.put_line ('-');
    END;
    PROMPT And see: someotherfield is indeed 'Y' so expected behavior
    SELECT test_ts_id, status, someotherfield,
    TO_CHAR (edittime, 'dd-mm-yyyy hh24:mi:ss') edittime
    FROM test_ts;
    Output on 10.2.0.1:
    Table dropped.
    Table created.
    Trigger created.
    Create one row, with status 1 and someotherfield initially 'N'
    1 row created.
    TEST_TS_ID STATUS S EDITTIME
    1 1 N 16-07-2006 15:11:35
    1 row selected.
    Update the row, with status 2 --> trigger logic will not fire
    Returned SomeOtherField (should be 'N' but is empty in 10.2.0.1): --> bug
    Returned EditTime (should be greater than selected one before): 16-07-2006 15:11:37
    PL/SQL procedure successfully completed.
    However: someotherfield is really 'N' so why is it returning NULL --> bug
    TEST_TS_ID STATUS S EDITTIME
    1 2 N 16-07-2006 15:11:37
    1 row selected.
    Update the row, with status 1 --> trigger logic will fire
    Returned SomeOtherField (should be 'Y' and is 'Y' also in 10.2.0.1): Y
    Returned EditTime (should be greater than selected one before): 16-07-2006 15:11:40
    PL/SQL procedure successfully completed.
    And see: someotherfield is indeed 'Y' so expected behavior
    TEST_TS_ID STATUS S EDITTIME
    1 1 Y 16-07-2006 15:11:40
    1 row selected.
    Output on 10.2.0.2:
    Table dropped.
    Table created.
    Trigger created.
    Create one row, with status 1 and someotherfield initially 'N'
    1 row created.
    TEST_TS_ID STATUS S EDITTIME
    1 1 N 16-07-2006 23:47:51
    1 row selected.
    Update the row, with status 2 --> trigger logic will not fire
    Returned SomeOtherField (should be 'N' and is indeed 'N' in 10.2.0.2): N --> ALLRIGHT, this correct, but look further...
    Returned EditTime (should be greater than selected one before): 16-07-2006 23:47:51
    PL/SQL procedure successfully completed.
    TEST_TS_ID STATUS S EDITTIME
    1 2 N 16-07-2006 23:47:54
    1 row selected.
    Update the row, with status 1 --> trigger logic will fire
    Returned SomeOtherField (should be 'Y' ...but is the old value 'N' in 10.2.0.2): N --> so a new bug has been introduced so a problem still remains!
    Returned EditTime (should be greater than selected one before): 16-07-2006 23:47:54
    PL/SQL procedure successfully completed.
    And see: someotherfield is indeed 'Y' so the Returned value is now not correct, like it was in 10.2.0.1
    TEST_TS_ID STATUS S EDITTIME
    1 1 Y 16-07-2006 23:47:56
    1 row selected.
    I am affraid we need to look at workarounds, because we rely heavily on before update triggers in the DB with conditional logic. I do not really want to change my triggers (for example removing conditional logic...). And it seems that waiting for the Oracle RDBMS to really solve this problem is not viable either (I saw notes that it will be solved in 11G, not in 10 or 9!).
    Anyone from the ADF development team that recognizes this problem and is able to verify that this really is a RDBMS problem? The testcases above run on every DB version as a regular user (for example SCOTT) with some create privileges),
    Toine

  • Problem creating user in RDBMS realm Using com.bea.wlpi.rdbmsrealm.RDBMSRealm

    Hi,
    I am currently using WLI 2.0 SP2 installation. Here is a very unusual thing I
    noticed. Can somebody tell me what is going on ???
    1 : I have set up the security realm as indicated in the config.xml file. As far
    as I understand, the caching realm entry has attribute pointing to the wlpiRDBMSRealm,
    which is a RDBMS implementation from the WLI 2.0 SP2 distribution.
    2: I start the server, open the WLS console, and create a new user through the
    console. I get no error message and it seems to work fine. ( I also click on the
    save it to database link, and it returns with msg that cache is refreshed ).
    3: I see an entry in the fileRealm.properties file, but no record is inserted
    in the WLSUSER table in the database.
    Since the RDBMS realm (from WLI distribution) is defined as basic
    realm implementation, should it not insert entry into the database, instead of
    the file realm.
    Is this a general problem ( any RDBMS realm ) or is it specific to the WLI ?
    Is there anything that I have not configured here that is causing this behavior
    Is it just refreshing the cache instead of inserting record in DB ?
    Why should it insert entry into fileRealm.properties ?
    Thanks,
    Girish
    [noaa1.zip]

    Hi,
    I turned on the caching realm through the WLS Console, (Security).
    After this I get a very unusual error, which seems to be comming
    from the RDBMS implementation class (from WLI 2.0 SP2 distribution).
    Here is the msg that I get while WLS server boots (the WLS server boots ok, but
    WLPI does not initialize) ....
    Unable to initialize WebLogic Process Integrator:
    SQL Exception: ResultSet not open, operation 'next' not permitted. Verify that
    autocommit is OFF.
    at c8e.k.j.l_(Unknown Source)
    at c8e.k.j.l_(Unknown Source)
    at c8e.k.j.j_(Unknown Source)
    at c8e.k.n.checkIfClosed(Unknown Source)
    at c8e.k.n.movePosition(Unknown Source)
    at c8e.k.n.movePosition(Unknown Source)
    at c8e.k.n.next(Unknown Source)
    at com.bea.wlpi.rdbmsrealm.RDBMSDelegate.getGroup(RDBMSDelegate.java:425)
    at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getGroup(RDBMSRealm.java:235)
    at weblogic.security.acl.CachingRealm.getGroup(CachingRealm.java:1120)
    at weblogic.ejb20.deployer.SecurityRoleMapping.lookupPrincipal(SecurityRoleMapping.java:243)
    at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:96)
    at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:128)
    at weblogic.ejb20.deployer.SecurityRoleMapping.isPrincipalInAnyRole(SecurityRoleMapping.java:174)
    at weblogic.ejb20.deployer.MethodInfoImpl.checkAccess(MethodInfoImpl.java:214)
    at weblogic.ejb20.internal.MethodDescriptor.checkAccess(MethodDescriptor.java:285)
    at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:90)
    at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:55)
    at com.bea.wlpi.server.plugin.PluginManagerCfgBeanEOImpl.init(PluginManagerCfgBeanEOImpl.java:1301)
    at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListenerBean.java:151)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:221)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:175)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1933)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1892)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.Kernel.execute(Kernel.java:250)
    at weblogic.jms.client.JMSSession.pushEnvelope(JMSSession.java:1779)
    at weblogic.jms.client.JMSCallback.pushEnvelope(JMSCallback.java:69)
    at weblogic.jms.frontend.FESession.execute(FESession.java:1972)
    <Aug 22, 2001 11:56:01 AM MDT> <Notice> <WebLogicServer> <WebLogic Server started>
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    com.bea.wlpi.rdbmsrealm.RDBMSException: caught SQL exception - with nested exception:
    [SQL Exception: ResultSet not open, operation 'next' not permitted. Verify that
    autocommit is OFF.]
    at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getGroup(RDBMSRealm.java:242)
    <Aug 22, 2001 11:56:01 AM MDT> <Notice> <WebLogicServer> <ListenThread listening
    on port 7101>
    at weblogic.security.acl.CachingRealm.getGroup(CachingRealm.java:1120)
    at weblogic.ejb20.deployer.SecurityRoleMapping.lookupPrincipal(SecurityRoleMapping.java:243)
    at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:96)
    at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:128)
    at weblogic.ejb20.deployer.SecurityRoleMapping.isPrincipalInAnyRole(SecurityRoleMapping.java:174)
    at weblogic.ejb20.deployer.MethodInfoImpl.checkAccess(MethodInfoImpl.java:214)
    at weblogic.ejb20.internal.MethodDescriptor.checkAccess(MethodDescriptor.java:285)
    at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:90)
    at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:55)
    at com.bea.wlpi.server.plugin.PluginManagerCfgBeanEOImpl.init(PluginManagerCfgBeanEOImpl.java:1301)
    at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListenerBean.java:151)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:221)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:175)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1933)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1892)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.Kernel.execute(Kernel.java:250)
    at weblogic.jms.client.JMSSession.pushEnvelope(JMSSession.java:1779)
    at weblogic.jms.client.JMSCallback.pushEnvelope(JMSCallback.java:69)
    at weblogic.jms.frontend.FESession.execute(FESession.java:1972)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "Girish Gupte" <[email protected]> wrote:
    >
    >
    >
    Hi,
    I am currently using WLI 2.0 SP2 installation. Here is a very unusual
    thing I
    noticed. Can somebody tell me what is going on ???
    1 : I have set up the security realm as indicated in the config.xml file.
    As far
    as I understand, the caching realm entry has attribute pointing to the
    wlpiRDBMSRealm,
    which is a RDBMS implementation from the WLI 2.0 SP2 distribution.
    2: I start the server, open the WLS console, and create a new user through
    the
    console. I get no error message and it seems to work fine. ( I also click
    on the
    save it to database link, and it returns with msg that cache is refreshed
    3: I see an entry in the fileRealm.properties file, but no record is
    inserted
    in the WLSUSER table in the database.
    Since the RDBMS realm (from WLI distribution) is defined as basic
    realm implementation, should it not insert entry into the database, instead
    of
    the file realm.
    Is this a general problem ( any RDBMS realm ) or is it specific to the
    WLI ?
    Is there anything that I have not configured here that is causing this
    behavior
    Is it just refreshing the cache instead of inserting record in DB ?
    Why should it insert entry into fileRealm.properties ?
    Thanks,
    Girish

  • Problem with weblogic-cmp-rdbms-jar.xml

    While using ANT by apache to create a deployable EAR file for my application i
    created the weblogic-cmp-rdbms-jar.xml file with the following DOCTYPE header
    <!DOCTYPE weblogic-rdbms-bean PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0
    EJB RDBMS20 Persistence//EN' 'http://www.bea.com/servers/wls600/dtd/weblogic-rdbms20-persistence-600.dtd'>
    when i go for ejbc following error is displayed
    [java] ERROR: Error from ejbc: Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml'.
    The error was:
    [java] weblogic.xml.process.ProcessorFactoryException: The public id, "-//BEA
    Systems, Inc.//DTD WebLogic 6.0.0 EJB RDBMS20 Persistence//EN", specified in the
    XML document is invalid. Use one of the following valid public ids:
    [java] "-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB RDBMS Persistence//EN"
    [java] "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB 1.1 RDBMS Persistence//EN"
    [java]
    [java] at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:239)
    [java] at weblogic.ejb20.cmp11.rdbms.Deployer.parseXMLFile(Deployer.java:293)
    [java] at weblogic.ejb20.cmp11.rdbms.Deployer.readTypeSpecificData(Deployer.java:358)
    [java] at weblogic.ejb20.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.ja
    va:482)
    [java] at weblogic.ejb20.persistence.PersistenceType.setupDeployer(PersistenceType.java:406
    [java] at weblogic.ejb20.deployer.CMPInfoImpl.setup(CMPInfoImpl.java:139)
    [java] at weblogic.ejb20.ejbc.EJB11CMPCompiler.generatePersistenceSources(EJB11CMPCompiler.
    java:61)
    [java] at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:233)
    [java] at weblogic.ejbc20.runBody(ejbc20.java:360)
    [java] at weblogic.utils.compiler.Tool.run(Tool.java:79)
    [java] at weblogic.ejbc.main(ejbc.java:21)
    [java]
    [java] ERROR: ejbc found errors
    BUILD FAILED
    i have created the Doctype header after refering to the documentation available
    at http://edocs.bea.com/wls/docs61///////ejb/EJB_reference.html
    please help me as i am not able to find out the exact problem. i have also applied
    the ejb2.0 patch available for 6.0 which is supposed to enable the ejb2.0 related
    features
    Any help will be really appreciated
    thanx in advance
    Daljit

    Are you trying to make an EJB 1.1 CMP bean or an EJB 2.0 CMP bean.
    It looks like you have an EJB 1.1 ejb-jar.xml, but have requested an EJB 2.0 cmp descriptor.
    Take a look at examples/ejb/basic/containerManaged and ejb20/basic/containerManaged for the 2 examples.
    -- Rob
    Daljit Chauhan wrote:
    While using ANT by apache to create a deployable EAR file for my application i
    created the weblogic-cmp-rdbms-jar.xml file with the following DOCTYPE header
    <!DOCTYPE weblogic-rdbms-bean PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0
    EJB RDBMS20 Persistence//EN' 'http://www.bea.com/servers/wls600/dtd/weblogic-rdbms20-persistence-600.dtd'>
    when i go for ejbc following error is displayed
    [java] ERROR: Error from ejbc: Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml'.
    The error was:
    [java] weblogic.xml.process.ProcessorFactoryException: The public id, "-//BEA
    Systems, Inc.//DTD WebLogic 6.0.0 EJB RDBMS20 Persistence//EN", specified in the
    XML document is invalid. Use one of the following valid public ids:
    [java] "-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB RDBMS Persistence//EN"
    [java] "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB 1.1 RDBMS Persistence//EN"
    [java]
    [java] at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:239)
    [java] at weblogic.ejb20.cmp11.rdbms.Deployer.parseXMLFile(Deployer.java:293)
    [java] at weblogic.ejb20.cmp11.rdbms.Deployer.readTypeSpecificData(Deployer.java:358)
    [java] at weblogic.ejb20.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.ja
    va:482)
    [java] at weblogic.ejb20.persistence.PersistenceType.setupDeployer(PersistenceType.java:406
    [java] at weblogic.ejb20.deployer.CMPInfoImpl.setup(CMPInfoImpl.java:139)
    [java] at weblogic.ejb20.ejbc.EJB11CMPCompiler.generatePersistenceSources(EJB11CMPCompiler.
    java:61)
    [java] at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:233)
    [java] at weblogic.ejbc20.runBody(ejbc20.java:360)
    [java] at weblogic.utils.compiler.Tool.run(Tool.java:79)
    [java] at weblogic.ejbc.main(ejbc.java:21)
    [java]
    [java] ERROR: ejbc found errors
    BUILD FAILED
    i have created the Doctype header after refering to the documentation available
    at http://edocs.bea.com/wls/docs61///////ejb/EJB_reference.html
    please help me as i am not able to find out the exact problem. i have also applied
    the ejb2.0 patch available for 6.0 which is supposed to enable the ejb2.0 related
    features
    Any help will be really appreciated
    thanx in advance
    Daljit

  • "How to Resolve ORA-29532 Java 2 Permission Problems in RDBMS 8.1.6 and 8.1.7"

    I'm in the process of publishing the following note (134280.1), titled "How to Resolve ORA-29532 Java 2
    Permission Problems in RDBMS 8.1.6 and 8.1.7".
    It will be accessible from Oracle Support's "Metalink" site.
    "How to Resolve ORA-29532 Java 2 Permission Problems in RDBMS 8.1.6 and 8.1.7".
    Problem Description
    Periodically an application running in the Enterprise Java Engine
    (EJE) formerly known as the "Oracle 8i JVM", "the JSERVER component", or
    the "Aurora JVM" will fail with a "java 2" permissions error having the
    following format :
    Note : Message shown below have been reformatted for easier readability.
    java.sql.SQLException: ORA-29532: Java call terminated by uncaught Java exception:
    usually followed by a detailed error message similar to one of the following
    messages :
    Example # 1
    java.security.AccessControlException: the Permission
    (java.net.SocketPermission hostname resolve)
    has not been granted by dbms_java.grant_permission to
    SchemaProtectionDomain(SCOTT|PolicyTableProxy(SCOTT))
    Example # 2
    java.security.AccessControlException: the Permission
    (java.util.PropertyPermission * read,write)
    has not been granted by dbms_java.grant_permission to
    SchemaProtectionDomain(SCOTT|PolicyTableProxy(SCOTT))
    Example # 3
    java.security.AccessControlException: the Permission
    (java.io.FilePermission \matt1.gif read)
    has not been granted by dbms_java.grant_permission to
    SchemaProtectionDomain(SCOTT|PolicyTableProxy(SCOTT))
    Explanation
    The java 2 permission stated in line # 2 of each of the above "Examples"
    has not been granted to the user specified in line 4 of the above "Examples".
    Solution Description
    The methodology to solve this issue is identical for all java 2 permissions
    cases.
    1) Format a call "dbms_java.grant_permission" procedure as described below.
    2) Logon as SYS or SYSTEM
    3) Issue the TWO commands shown below
    4) Logoff as SYS or SYSTEM
    5) Retry your application
    For Example # 1
    1) Logon as SYS or SYSTEM
    2) Issue the following commands :
    a) call dbms_java.grant_permission('SCOTT',
    'java.net.SocketPermission',
    'hostname',
    'resolve');
    b) commit;
    Note: Commit is mandatory !!
    3) Logoff as SYS or SYSTEM
    4) Retry your application
    For Example # 2
    1) Logon as SYS or SYSTEM
    2) Issue the following commands :
    a) call dbms_java.grant_permission('SCOTT',
    'java.util.PropertyPermission',
    'read,write');
    b) commit;
    Note: Commit is mandatory !!
    3) Logoff as SYS or SYSTEM
    4) Retry your application
    For Example # 3
    1) Logon as SYS or SYSTEM
    2) Issue the following commands :
    a) call dbms_java.grant_permission('SCOTT',
    'java.io.FilePermission',
    '\matt1.gif',
    'read');
    b) commit;
    Note: Commit is mandatory !!
    3) Logoff as SYS or SYSTEM
    4) Retry your application
    References
    For more details on java 2 permissions and security within the EJE, review
    Chapter 5, in the Java Developer's Guide. entitled,
    "Security For Oracle8i Java Applications"
    The RDBMS 8.1.7 version can be found at :
    http://otn.oracle.com/docs/products/oracle8i/doc_library/817_doc/java.817/index.htm

    Hi, Don,
    I solved the problem of security exception I mentioned at java procedure topic as following:
    ORA-29532: Java call terminated by uncaught Java exception: java.lang.SecurityException
    I tried to use your solution as following:
    call dbms_java.grant_permission('SDE', 'java.net.SocketPermission', 'ORCL.COHPA.UCF.EDU','resolve');
    but SQL*plus gave me a error message:
    invalid collumn.
    What's the problem?
    However, I call a grant command as following:
    SQL> grant JAVASYSPRIV to sde;
    and then that exception is gone. What's the difference between dbms_java.grant_permission and grant command?
    Thanks
    Bing
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by don -- oracle support:
    I'm in the process of publishing the following note (134280.1), titled "How to Resolve ORA-29532 Java 2
    Permission Problems in RDBMS 8.1.6 and 8.1.7".
    It will be accessible from Oracle Support's "Metalink" site.
    "How to Resolve ORA-29532 Java 2 Permission Problems in RDBMS 8.1.6 and 8.1.7".
    Problem Description
    <HR></BLOCKQUOTE>
    null

  • Problems trying to use built-in OWB 11.2 on Oracle RDBMS 11.2 (64 bit)

    I recently installed Oracle Enterprise RDBMS 11.2.0.1.0 (64 bit) on my 64-bit Windows 7 machine. I'm now trying to get the built-in OWB 11.2 installation working as well. I managed to create a repository on my database using the Repository Assistant. But I can't seem to get OWB Design Center to run at all: it crashes out with a Windows message "application cannot be started" as soon as it tries to run owbclient.bat.
    I've tried starting the Control Center Service via the options on the Warehousebuilder/Admin menu, and this seems to work - at least the status comes back as "available" when I click the "Check status" button - but the Repository Browser doesn't work either: the URL looks OK but there's nothing there.
    As far as I can tell I've followed the installation/configuration steps OK, but I can't work out what else I need to install/do to get an OWB client talking to a local OWB installation on a local Oracle 11.2 database. It really shouldn't be this hard.
    Has anybody else encountered/resolved the same problems?
    Or should I just scrap my installation and start again from scratch?

    Thanks, Richard.
    I downloaded Oracle 11gR2 for 64-bit Windows only a couple of weeks ago, so I would have expected the built-in OWB client installation to be compatible with 64-bit Windows as well. Maybe that's just a crazy dream.
    In the end, I gave up on the built-in OWB. Instead, I trashed the existing OWB installation in the database completely, then installed the OWB stand-alone client in a separate home on the same machine instead, re-installing the OWB schemas etc and creating a fresh repository on the DB in the process. This seems to work so far - at least I can log in to the OWB Design Center client as my repository user, which is a major step forward.
    I dunno - I've been working with Oracle for 20 years, but their installation processes always seems to trip me up somewhere with missing components, incompatible elements, screwed up network addresses, and so on. Guess I'm just a slow learner.

  • Problems about 8i on solaris2.6 $ORACLE_HOME/rdbms/lib/ins_r

    When i tried to install O8i for solaris (CD from OTN )on Sun
    Solaris 2.6,I've met such problems:
    Error in invoking target install of makefile
    $ORACLE_HOME/rdbms/lib/ins_rbms.mk
    C Complier used:/usr/ccs/bin/cc,make
    I appreciate your help
    null

    Check permissions in /usr/ccs/bin. I had the same problem due to set id bit being set on all binaries in this directory. Consequently, it runs as 'bin', who doesn't have permission to write in the 'oracle' directories.
    Ps. Mubashir. Oliver posted this to this group as there does't appear to be a Solaris 8i install group. So check you facts before you get smart.
    null

  • RDBMS Code generator Problem!!!

    I use weblogic.ejbc to compile my bean but it has an error "Code too long" with try-catch block in myprogram_Weblogic_CMP_RDBMS.java....
    What's the problem becouse ejbc generate that file from my weblogig-cmp-rdbms-jar.xml.
    I use Weblogic 6.0 service pack 2 and include ejb20.jar and ejb.jar
    How can I do that? Please help.
    Thankyou

    Repost in the CMP section.
    (BTW - I think that there is a -keepgenerated option so you can see the
    .java.)
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    Clustering Weblogic? You're either using Coherence, or you should be!
    Download a Tangosol Coherence eval today at http://www.tangosol.com/
    "Chutatuch Hemarat" <[email protected]> wrote in message
    news:3c5a4c58$[email protected]..
    I use weblogic.ejbc to compile my bean but it has an error "Code too long"with try-catch block in myprogram_Weblogic_CMP_RDBMS.java....
    What's the problem becouse ejbc generate that file from myweblogig-cmp-rdbms-jar.xml.
    I use Weblogic 6.0 service pack 2 and include ejb20.jar and ejb.jar
    How can I do that? Please help.
    Thankyou

  • Rdbms patchset problem in installing metadata repository

    hi ,
    i m facing this problem while installing metadata repository for Oracle Application Server10g(9.0.4.0.0)
    the error is ,
    "the catalog objects stored in this database donot have the same version as the database software.
    please review the post-installation steps of the RDBMS patchset and make sure that you have run
    all required SQL scripts."
    plz help

    Hello,
    You can login to the Metadata database and execute:
    select * from dba_registry;
    This will give you the version numbers for database components.
    Vlad

  • Problems creating RDBMS Event Generators in a WebLogic cluster

    Hi Everybody,
    I just set up an integration cluster with one admin server and two managed servers into only one computer.
    My deployed Application needs an RDBMS Event generator with 5 channel rules to be created and when I create the first channel rule I get this exception:
    java.lang.NullPointerException
    at com.bea.wli.management.configuration.RDBMSEventGenChannelConfiguration.equals(RDBMSEventGenChannelConfiguration.java:285)
    at java.util.LinkedList.indexOf(LinkedList.java:398)
    at java.util.LinkedList.contains(LinkedList.java:176)
    at java.util.AbstractCollection.removeAll(AbstractCollection.java:354)
    at com.bea.wli.management.mbconnector.rdbms.RDBMSEventGenConfigManager.setChannels(RDBMSEventGenConfigManager.java:886)
    at com.bea.wli.management.mbconnector.GenericEventGenConfigurationMBeanImpl.setChannels(GenericEventGenConfigurationMBeanImpl.java:59)
    at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
    at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1662)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1109)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:372)
    at com.bea.wli.management.internal.WLIConfigurationMBeanImpl.setAttribute(WLIConfigurationMBeanImpl.java:152)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_setAttribute(RemoteMBeanServerImpl.java:431)
    at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:387)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:735)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:469)
    at com.bea.wli.management.configuration.GenericEventGenConfigurationMBean_Stub.setChannels([Lcom.bea.wli.management.configuration.GenericEventGenChannelConfiguration;)V(Unknown Source)
    at com.bea.wli.oam.eg.framework.XEGHelper.updateEventGenerator(XEGHelper.java:243)
    at com.bea.wli.oam.eg.framework.XEGMainServlet.saveGenerator(XEGMainServlet.java:709)
    at com.bea.wli.oam.rdbmseg.RDBMSMainServlet.submitChannel(RDBMSMainServlet.java:349)
    at com.bea.wli.oam.eg.framework.XEGMainServlet.processRequest(XEGMainServlet.java:88)
    at com.bea.wli.oam.eg.framework.XEGMainServlet.doPost(XEGMainServlet.java:151)
    at com.bea.wli.oam.core.BaseServlet.userService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(Unknown Source)
    at com.bea.wli.oam.core.BaseServlet.run()Ljava.lang.Object;(Unknown Source)
    at
    The funny thing is that in my one server development / test production environment I don't have any problems at the time of the RDBMS Event generators...
    Please anyone can help me? Any special JMS queue need to be created or something?? I'm becoming desperate!!
    Thank you all!
    Oscar                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Well
    At last I've found the answer...
    In order to successfully create an RDBMS Event Generator, the creation app (in this case, wliconsole) must have access to the destination datasource. Thus, both connection pool and datasource targeted by the RDBMS EG must be deployed in the same server running the wliconsole.
    In this particular case, I just had to redeploy my datasources targetting all servers in the cluster plus the admin server and that's it...
    See you...
    O.

  • RDBMS adapter, stored procedure and refcursor problem

              Hi !
              I am trying to use the RDBMS adapter for 8.1 SP2 to retreive data from a stored
              procedure having an out parameter of the refcursor type. This service is impossible
              to define in WLAI, any suggestions, sample code would be greately appreciated.
              Regards,
              Anders Mathisen
              

    Unless you are running a really old version of Oracle, any weak ref cursor can just be declared SYS_REFCURSOR. Also, you can't use a weak ref cursor for %ROWTYPE. You can test the procedure in SQL*Plus by using it to populate a refcursor variable.

Maybe you are looking for

  • How do I update apps that we're originally downloaded w/ non-email Apple ID?

    I have some apps on my iPhone thar I downloaded before an email address was required your Apple ID. Now that an email address is required I can't run updates on those apps from the app store because the apps still have my old username associated with

  • Cant connect to Airport Express or Apple TV

    After I upgraded I cant connect my Itunes to Airport Express (the option on the bottom is gone) ... nor can I connect to AppleTV. What can be wrong???? Please help!

  • Ipod touch stopped working

    I bought an Iphone yesterday and my daughter says that since I got home she is having trouble sending messages from her ipod touch. Does anyone know why? She said the icloud isnt working, but I didnt activate the icloud on my phone until this morning

  • Menu bar trouble, only with IE

    Hi, I've just built a website for my business from scratch using Dreamweaver CS5 having had no previous experience with web design; this is my first site. I have uploaded the files and the website works as expected on all the main browsers except Int

  • Office Jet Pro 8000 Does Not Recognize Legal Paper

    I have an Officejet Pro 8000 and added a second paper tray for legal paper.  I know I'm not doing something simple but can't remember how to get printer preferences to show both letter and legal for available paper.  I chatted with tech support for a