Expdp fail and create table SYS_EXPORT_SCHEMA_20

Hi Gurus
I am using Oracle 10.2.0.3 in AIX env
My database size is around 1600 GB. Sometime my expdp fail and create table like SYS_EXPORT_SCHEMA_20, SYS_EXPORT_SCHEMA_05. As I run expdp from system user , I notice that it create this type of table into system tablespace. It time it consume around 5gb space. Now my system tablespace size is 68 GB.
Can I drop those table? If I drop these table then it create any problem? This is my production database.
Regards
Rabi

user13134974 wrote:
Hi Gurus
I am using Oracle 10.2.0.3 in AIX env
Regards
RabiThose tables you were mentioning, SYS_EXPORT_SCHEMA_nn , are the data pump master tables used for data pump jobs;their purpose is to
hold the info about the job details.
Once the job has finished table should be droped, but in case of a job failure table remains so every new dp job must create new SYS_EXPORT_SCHEMA_nn table
with the +1 nn iteration depending on the name of the last master table that was left due to the dp job failure.
Cleaning those tables can be done with the dbms_datapump STOP_JOB Procedure, check the docs about the details :
http://download.oracle.com/docs/cd/B12037_01/server.101/b10825/dp_export.htm
You can also go visit youroracle support to see examples and instructions for cleaning your db from those dismised master tables,
How To Cleanup Orphaned DataPump Jobs In DBA_DATAPUMP_JOBS ? [ID 336014.1]

Similar Messages

  • Way to programmatically drop-and-create-tables?

    Hi all,
    I have a persistence unit which exists to provide lookup information to my application. It is populated by data that is available at runtime. It takes a long time to parse this data, and therefore my intention is to only parse it once at the deployment target. To do this, I have created a main method that does all the parsing, and I do not set the toplink.ddl-generation property in persistence.xml. This causes the application to fail if the database is not created.
    However, this means that during the population stage, I must drop and create any existing tables. I had thought it would be possible to do this by obtaining an EntityManagerFactory which has a property map sent to it, containing the property toplink.ddl-generation set to drop-and-create-tables. But this does not work... the tables are not dropped (if they exist) and are not created (if the database is empty).
    Is it possible to do the drop-and-create-tables programmatically using the JPA?
    I may have another EntityManagerFactory open at the same time, which has been opened with the default options... would this be conflicting?

    I don't think there is any easy way to generate the default tables once your have created the EntityManagerFactory. You could use the EclipseLink/TopLink schemaframework or TableCreator to create tables using a EclipseLink/TopLink DatabaseSession.
    There is a DefaultTableGenerator in org.eclipse.persistence.tools.schemaframework, which may give you what you are looking for.
    -- James : http://www.eclipselink.org

  • Insert, select and create table as give different results

    Hi all
    I have a strange situation with this three cases:
    1) select statement: SELECT (...)
    2) insert statement with that same select as above: INSERT INTO SELECT (...)
    3) create table statement again with that same select: CREATE TABLE AS SELECT (...)
    Each of these cases produce different number of rows (first one 24, second 108 and third 58). What's more the data for second and third case doesn't have any sense with what they should return. The first case returns good results.
    One interesting thing is that select uses "UNION ALL" between 2 queries. When simple UNION is used, everything works fine and all three cases return 24 rows. Also if each query is run seaprately, they work fine.
    Anyone encountered something like this? (before i create an SR :)
    Database is 10.2.0.2 on AIX 5.3. It's a data warehouse.
    Edited by: dsmoljanovic on Dec 10, 2008 3:57 PM

    I understand UNION vs UNION ALL. But that doesn't change the fact that same SELECT should return same set of rows wether in INSERT, CREATE TABLE AS or a simple SELECT.
    DB version is 10.2.0.2.
    Here is the SQL:
    INSERT INTO TMP_TRADING_PROM_BM_OSTALO
    select
    5 AS VRSTA_PLANIRANJA_KLJUC, u1.UNOS_KLJUC, t1.TRADING_TIP_KLJUC, i1.IZVOR_KLJUC, m1.ITEMNAME AS MJESEC,
    l1.PLAN AS IZNOS, l1.TEKUA AS TEKUCA, l1.PROLA AS PROSLA, l1.PLANTEKUA_ AS IZNOS_TEKUCA, l1.PLANPROLA_ AS IZNOS_PROSLA, l1.TEKUAPROLA_ AS TEKUCA_PROSLA, l1.DATUM_UCITAVANJA
    from
    HR_SP_PLAN.L_12_ET_PROMETI_I_BRUTO_MARZA l1,
    select
    m1.ITEMIID, m1.ITEMNAME
    from
    HR_SP_PLAN.L_12_IT_4_MJESECI m1
    where
    UPPER (m1.ITEMNAME) NOT LIKE '%KVARTAL%' AND UPPER (m1.ITEMNAME) NOT LIKE '%GODINA%' AND UPPER (m1.ITEMNAME) NOT LIKE '%PROC%' and
    m1.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy')
    union all
    select -99, null from dual
    ) m1,
    HR_SP_PLAN.L_12_IT_5_SEKTORI l2,
    HR_SP_PLAN.L_12_IT_2_TIPOVI_OSTALO l3, HR_SP_PLAN.D_UNOS u1, HR_SP_PLAN.D_TRADING_TIP t1, HR_SP_PLAN.L_12_IT_1_PROMET_I_BM_OSTALO p1, HR_SP_PLAN.D_IZVOR i1
    where
    l1.ELIST = l2.ITEMIID and
    l2.ITEMNAME = u1.UNOS_NAZIV and u1.USER_KLJUC = 12 and l2.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
    l1.DIMENSION_1_PROMET = p1.ITEMIID and
    p1.ITEMNAME = i1.IZVOR_NAZIV and i1.USER_KLJUC = 12 and p1.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
    nvl(l1.DIMENSION_4_MJESEC , -99) = m1.ITEMIID and
    l1.DIMENSION_2_TIPOVI = l3.ITEMIID and
    l3.ITEMNAME = t1.TRADING_TIP_NAZIV and l3.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
    l1.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
    'PROC' = 'PLAN'
    union all
    select
    4 AS VRSTA_PLANIRANJA_KLJUC, u1.UNOS_KLJUC, t1.TRADING_TIP_KLJUC, i1.IZVOR_KLJUC, m1.ITEMNAME AS MJESEC,
    l1.PROCJENA AS IZNOS, l1.TEKUA AS TEKUCA, l1.PROLA AS PROSLA, l1.PROCJENATEKUA_ AS IZNOS_TEKUCA, l1.PROCJENAPROLA_ AS IZNOS_PROSLA, l1.TEKUAPROLA_ AS TEKUCA_PROSLA, l1.DATUM_UCITAVANJA
    from
    HR_SP_PLAN.L_13_ET_PROMETI_I_BRUTO_MARZA l1,
    select
    m1.ITEMIID, m1.ITEMNAME
    from
    HR_SP_PLAN.L_13_IT_4_MJESECI m1
    where
    UPPER (m1.ITEMNAME) NOT LIKE '%KVARTAL%' AND UPPER (m1.ITEMNAME) NOT LIKE '%GODINA%' AND UPPER (m1.ITEMNAME) NOT LIKE '%PROC%' and
    nvl(ceil(to_number(m1.ITEMNAME)/3), mod(4, 5)) = mod(4, 5) and m1.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy')
    union all
    select -99, null from dual
    ) m1,
    HR_SP_PLAN.L_13_IT_5_SEKTORI l2, HR_SP_PLAN.L_13_IT_2_TIPOVI_OSTALO l3,
    HR_SP_PLAN.D_UNOS u1, HR_SP_PLAN.D_TRADING_TIP t1,
    HR_SP_PLAN.L_13_IT_1_PROMET_I_BM_OSTALO p1, HR_SP_PLAN.D_IZVOR i1
    where
    l1.ELIST = l2.ITEMIID and
    l2.ITEMNAME = u1.UNOS_NAZIV and u1.USER_KLJUC = 13 and l2.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
    l1.DIMENSION_1_PROMET = p1.ITEMIID and
    p1.ITEMNAME = i1.IZVOR_NAZIV and i1.USER_KLJUC = 13 and p1.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
    nvl(l1.DIMENSION_4_MJESEC , -99) = m1.ITEMIID and
    l1.DIMENSION_2_TIPOVI = l3.ITEMIID and
    l3.ITEMNAME = t1.TRADING_TIP_NAZIV and l3.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
    l1.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
    'PROC' = 'PROC';

  • How to create stored procedure to drop and create table

    Version: Oracle 10g
    I am trying to create a stored procedure that will drop and create a table based on a select statement. I can create the table but I can't drop it.
    CREATE OR REPLACE procedure EC_LOAD is
    begin
    INSERT INTO Sales_table
    (FSCL_WK,
    DIV,
    ACCT_TYPE)
    Select
    FSCL_WK,
    DIV,
    ACCT_TYPE
    from
    sales_revenue;
    end ecload;
    I need to drop Sales_table before inserting the values. How do i do this?

    Or with a drop:
    SQL> desc emp2
    ERROR:
    ORA-04043: object emp2 does not exist
    SQL>
    SQL> declare
      2    cnt      int := 0;
      3  begin
      4    select max (1)
      5      into cnt
      6      from user_tables
      7     where table_name = 'EMP2';
      8
      9    if cnt = 1
    10    then
    11      execute immediate 'drop table emp2';
    12    end if;
    13
    14    execute immediate 'create table emp2 as select * from emp';
    15  end;
    16  /
    PL/SQL procedure successfully completed.
    SQL>
    SQL> desc emp2
    Name                                      Null?    Type
    EMPNO                                              NUMBER(4)
    ENAME                                              VARCHAR2(10)
    JOB                                                VARCHAR2(9)
    MGR                                                NUMBER(4)
    HIREDATE                                           DATE
    SAL                                                NUMBER(7,2)
    COMM                                               NUMBER(7,2)
    DEPTNO                                             NUMBER(2)
    SQL>

  • PLSQL and Create Table

    Hi
    I was wondering whether someone would help me with my first ever piece of PLSQL. I am trying to embed a create table as select statement into a PLSQL loop so that I can create a number of tables automatically. I am unclear as to whether this is possible or not, but my attempts so far has been unsucessful. My code so far is as follows:
    declare
    l_loops number :=1;
    begin
    loop
    if l_loops > 4 then
    exit;
    end if;
    create table l_loops as select year, month from caadatanum
    where month = l_loops;
    l_loops := l_loops +1;
    end loop;
    end;
    I am trying to use the loop to change the where condition
    as it loops through. The error message I get tells me
    that it doesn't expect the create statement so I am quite confused. Any help anyone could give me would be greatly appreciated.
    Thanks
    John

    Hi
    Firstly can I thanks you all for your help. The code no runs ok apart from one thing. It concerns the labelling of the table itself
    so 'create table '||l_loops||' as select ...
    errors with invalid table name presumably because it doesn't like giving tables numbers as names. I have tried
    'create table '||to_char(l_loops)||' as select .. but to no avail
    Is it possible to concatenate the l_loops number with a string somehow to get the statement to work ?
    create table mytable||'||l_loops||' doesn't work so I am not really sure what to do.
    Once again thanks
    John

  • Expdp fails to create .dmp files in NFS mount point in solaris 10,Oracle10g

    Dear folks,
    I am facing a wierd issue while doing expdp with NFS mount point. Kindly help me on this.
    ===============
    expdp system/manager directory=exp_dumps dumpfile=u2dw.dmp schemas=u2dw
    Export: Release 10.2.0.4.0 - 64bit Production on Wednesday, 31 October, 2012 17:06:04
    Copyright (c) 2003, 2007, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORA-39001: invalid argument value
    ORA-39000: bad dump file specification
    ORA-31641: unable to create dump file "/backup_db/dumps/u2dw.dmp"
    ORA-27040: file create error, unable to create file
    SVR4 Error: 122: Operation not supported on transport endpoint
    I have mounted like this:
    mount -o hard,rw,noac,rsize=32768,wsize=32768,suid,proto=tcp,vers=3 -F nfs 172.20.2.204:/exthdd /backup_db
    NFS=172.20.2.204:/exthdd
    given read,write grants to public as well as specific user

    782011 wrote:
    Hi sb92075,
    Thanks for ur reply. pls find the below. I am able to touch the files while exporting log files also creating having the error msg as i showed in previous post.
    # su - oracle
    Sun Microsystems Inc. SunOS 5.10 Generic January 2005
    You have new mail.
    oracle 201> touch /backup_db/dumps/u2dw.dmp.test
    oracle 202>I contend that Oracle is too dumb to lie & does not mis-report reality
    27040, 00000, "file create error, unable to create file"
    // *Cause:  create system call returned an error, unable to create file
    // *Action: verify filename, and permissions                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Find/Change Item Numbers and create Table of Contents

    Hello! I need help to find all my item numbers and apply a paragraph style to it so I can use them to create a Table of Contents page.
    Sample item numbers
    #12345
    #12345-5
    #12345-20
    #12345-ABC
    #12345/N
    I tried entering #^?^?^?^?^? on the Find/Change box and but this will find exactly the 5 characters after the # sign. I wonder if you can find all characters starting with # and until the last characters.
    Once I find all the item numbers, how can I apply the paragraph style for only those characters after the # sign? Because I only want to show the item numbers without the # sign on the Table of contents/Index page.
    By the way, I have InDesign CS2 which have no GREP function Maybe I can do this without the GREP?
    I really appreciate any help. Thank you very much.

    You actually have two problems here. The first is to assign the paragraph style. For that you can use GREP.
    Find #\d+ and leave the change field blank, but in the change formatting pick the paragraph style. Stricly speaking you only need to find #\d or even just # because a paragraph style applies to an entire paragraph, so assigning it to any character inthe paragraph will assign it to the entire paragraph.
    Which is your second problem. The TOC is based on paragraph styles and will include all of the text in each paragraph (up to the character limit for a TOC entry, which I think is 256 characters). You can't make a TOC and only use some of the paragraph. For that you need to use an index, or you need to make hidden or non-pinting frames with only the exact text you want in the TOC and assign a unique style to those.
    It's also possible someone has written (or could write) a script that can find text strings that match a pattern such as your numers, assign a character style to them (you could actually do that part in the paragraph style by adding a nested GREP style), then making a list of the text strings along with the page number on which they appear -- almost the same as an index except it would be based on character style, not an index marker.

  • Failed to create table when deployment.

    Hello,
    When I deployed an EAR, it show the following exceptions. I am using WLS8.1
    in Win98 with PostgreSQL for win32.
    All my deployed Entity Beans are CMP.
    Please check the following exceptions, and please give me some idea how to
    solve it. Thanks a lot.
    Eric
    The time this task was completed.
    Exception: Exception:weblogic.management.ApplicationException: activate
    failed for macausms-ejb.jar Module: macausms-ejb.jar Error: Exception
    activating module: EJBModule(macausms-ejb.jar,status=PREPARED) Unable to
    deploy EJB: MessageRecord from macausms-ejb.jar: [EJB:011032]The container
    was unable to determine the java.sql.Types of database columns.
    weblogic.ejb20.WLDeploymentException: [EJB:011031]The Entity EJB requires
    the table: chk_messagerecord to be accessible. Please ensure that this table
    exists and is accessible. at
    weblogic.ejb20.utils.TableVerifier.verifyTable(TableVerifier.java:242) at
    weblogic.ejb20.utils.TableVerifier.verifyOrCreateOrAlterTable(TableVerifier.
    java:123) at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.populateFieldSQLTypeMap(RDB
    MSPersistenceManager.java:832) at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManag
    er.java:211) at
    weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
    at
    weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164) at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanIn
    foImpl.java:1004) at
    weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1320) at
    weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:606) at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContain
    er.java:3007) at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2071) at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2052) at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
    eContainer(SlaveDeployer.java:2558) at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDe
    ployer.java:2483) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
    a:2308) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
    loyer.java:2390) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
    va:2302) at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2455) at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:829) at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:538) at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:496) at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151) Unable to deploy
    EJB: MessageRecord from macausms-ejb.jar: [EJB:011032]The container was
    unable to determine the java.sql.Types of database columns.
    weblogic.ejb20.WLDeploymentException: [EJB:011031]The Entity EJB requires
    the table: chk_messagerecord to be accessible. Please ensure that this table
    exists and is accessible. at
    weblogic.ejb20.utils.TableVerifier.verifyTable(TableVerifier.java:242) at
    weblogic.ejb20.utils.TableVerifier.verifyOrCreateOrAlterTable(TableVerifier.
    java:123) at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.populateFieldSQLTypeMap(RDB
    MSPersistenceManager.java:832) at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManag
    er.java:211) at
    weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
    at
    weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164) at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanIn
    foImpl.java:1004) at
    weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1320) at
    weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:606) at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContain
    er.java:3007) at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2071) at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2052) at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
    eContainer(SlaveDeployer.java:2558) at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDe
    ployer.java:2483) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
    a:2308) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
    loyer.java:2390) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
    va:2302) at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2455) at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:829) at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:538) at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:496) at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151) at
    weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1379) at
    weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:606) at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContain
    er.java:3007) at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2071) at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2052) at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
    eContainer(SlaveDeployer.java:2558) at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDe
    ployer.java:2483) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
    a:2308) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
    loyer.java:2390) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
    va:2302) at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2455) at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:829) at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:538) at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:496) at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    The exception that occurred while performing this task.
    Log:
    A log of the task's activities.
    [Deployer:149033]preparing application macausms on myserver
    [Deployer:149033]prepared application macausms on myserver
    [Deployer:149033]activating application macausms on myserver
    [Deployer:149033]failed application macausms on myserver
    [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
    application macausms on myserver.:
    Exception:weblogic.management.ApplicationException: activate failed for
    macausms-ejb.jar
    Module: macausms-ejb.jar Error: Exception activating module:
    EJBModule(macausms-ejb.jar,status=PREPARED)
    Unable to deploy EJB: MessageRecord from macausms-ejb.jar:
    [EJB:011032]The container was unable to determine the java.sql.Types of
    database columns.
    weblogic.ejb20.WLDeploymentException: [EJB:011031]The Entity EJB requires
    the table: chk_messagerecord to be accessible. Please ensure that this table
    exists and is accessible.
    at weblogic.ejb20.utils.TableVerifier.verifyTable(TableVerifier.java:242)
    at
    weblogic.ejb20.utils.TableVerifier.verifyOrCreateOrAlterTable(TableVerifier.
    java:123)
    at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.populateFieldSQLTypeMap(RDB
    MSPersistenceManager.java:832)
    at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManag
    er.java:211)
    at
    weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
    at
    weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164)
    at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanIn
    foImpl.java:1004)
    at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
    at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:606)
    at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContain
    er.java:3007)
    at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2071)
    at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2052)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
    eContainer(SlaveDeployer.java:2558)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDe
    ployer.java:2483)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
    a:2308)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
    loyer.java:2390)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
    va:2302)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2455)
    at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:538)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:496)
    at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    Unable to deploy EJB: MessageRecord from macausms-ejb.jar:
    [EJB:011032]The container was unable to determine the java.sql.Types of
    database columns.
    weblogic.ejb20.WLDeploymentException: [EJB:011031]The Entity EJB requires
    the table: chk_messagerecord to be accessible. Please ensure that this table
    exists and is accessible.
    at weblogic.ejb20.utils.TableVerifier.verifyTable(TableVerifier.java:242)
    at
    weblogic.ejb20.utils.TableVerifier.verifyOrCreateOrAlterTable(TableVerifier.
    java:123)
    at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.populateFieldSQLTypeMap(RDB
    MSPersistenceManager.java:832)
    at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManag
    er.java:211)
    at
    weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
    at
    weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164)
    at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanIn
    foImpl.java:1004)
    at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
    at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:606)
    at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContain
    er.java:3007)
    at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2071)
    at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2052)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
    eContainer(SlaveDeployer.java:2558)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDe
    ployer.java:2483)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
    a:2308)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
    loyer.java:2390)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
    va:2302)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2455)
    at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:538)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:496)
    at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1379)
    at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:606)
    at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContain
    er.java:3007)
    at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2071)
    at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2052)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
    eContainer(SlaveDeployer.java:2558)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDe
    ployer.java:2483)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
    a:2308)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
    loyer.java:2390)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
    va:2302)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2455)
    at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:538)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:496)
    at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    ==========================
    If you know what you are doing,
    it is not called RESEARCH!
    ==========================
    ==========================
    If you know what you are doing,
    it is not called RESEARCH!
    ==========================

    You should post to the ejb.cmb newsgroup not here.
    Thanks
    mbg
    "Eric Chow" <[email protected]> wrote in message
    news:[email protected]...
    Hello,
    When I deployed an EAR, it show the following exceptions. I am usingWLS8.1
    in Win98 with PostgreSQL for win32.
    All my deployed Entity Beans are CMP.
    Please check the following exceptions, and please give me some idea how to
    solve it. Thanks a lot.
    Eric
    The time this task was completed.
    Exception: Exception:weblogic.management.ApplicationException: activate
    failed for macausms-ejb.jar Module: macausms-ejb.jar Error: Exception
    activating module: EJBModule(macausms-ejb.jar,status=PREPARED) Unable to
    deploy EJB: MessageRecord from macausms-ejb.jar: [EJB:011032]The container
    was unable to determine the java.sql.Types of database columns.
    weblogic.ejb20.WLDeploymentException: [EJB:011031]The Entity EJB requires
    the table: chk_messagerecord to be accessible. Please ensure that thistable
    exists and is accessible. at
    weblogic.ejb20.utils.TableVerifier.verifyTable(TableVerifier.java:242) at
    weblogic.ejb20.utils.TableVerifier.verifyOrCreateOrAlterTable(TableVerifier.
    java:123) at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.populateFieldSQLTypeMap(RDB
    MSPersistenceManager.java:832) at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManag
    er.java:211) at
    weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
    at
    weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164) at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanIn
    foImpl.java:1004) at
    weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1320) at
    weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:606) at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContain
    er.java:3007) at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2071) at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2052) at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
    eContainer(SlaveDeployer.java:2558) at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDe
    ployer.java:2483) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
    a:2308) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
    loyer.java:2390) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
    va:2302) at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2455) at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:829) at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:538) at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:496) at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151) Unable to deploy
    EJB: MessageRecord from macausms-ejb.jar: [EJB:011032]The container was
    unable to determine the java.sql.Types of database columns.
    weblogic.ejb20.WLDeploymentException: [EJB:011031]The Entity EJB requires
    the table: chk_messagerecord to be accessible. Please ensure that thistable
    exists and is accessible. at
    weblogic.ejb20.utils.TableVerifier.verifyTable(TableVerifier.java:242) at
    weblogic.ejb20.utils.TableVerifier.verifyOrCreateOrAlterTable(TableVerifier.
    java:123) at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.populateFieldSQLTypeMap(RDB
    MSPersistenceManager.java:832) at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManag
    er.java:211) at
    weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
    at
    weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164) at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanIn
    foImpl.java:1004) at
    weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1320) at
    weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:606) at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContain
    er.java:3007) at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2071) at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2052) at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
    eContainer(SlaveDeployer.java:2558) at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDe
    ployer.java:2483) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
    a:2308) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
    loyer.java:2390) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
    va:2302) at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2455) at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:829) at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:538) at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:496) at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151) at
    weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1379) at
    weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:606) at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContain
    er.java:3007) at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2071) at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2052) at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
    eContainer(SlaveDeployer.java:2558) at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDe
    ployer.java:2483) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
    a:2308) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
    loyer.java:2390) at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
    va:2302) at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2455) at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:829) at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:538) at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:496) at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    The exception that occurred while performing this task.
    Log:
    A log of the task's activities.
    [Deployer:149033]preparing application macausms on myserver
    [Deployer:149033]prepared application macausms on myserver
    [Deployer:149033]activating application macausms on myserver
    [Deployer:149033]failed application macausms on myserver
    [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
    application macausms on myserver.:
    Exception:weblogic.management.ApplicationException: activate failed for
    macausms-ejb.jar
    Module: macausms-ejb.jar Error: Exception activating module:
    EJBModule(macausms-ejb.jar,status=PREPARED)
    Unable to deploy EJB: MessageRecord from macausms-ejb.jar:
    [EJB:011032]The container was unable to determine the java.sql.Types of
    database columns.
    weblogic.ejb20.WLDeploymentException: [EJB:011031]The Entity EJB requires
    the table: chk_messagerecord to be accessible. Please ensure that thistable
    >
    exists and is accessible.
    at weblogic.ejb20.utils.TableVerifier.verifyTable(TableVerifier.java:242)
    at
    weblogic.ejb20.utils.TableVerifier.verifyOrCreateOrAlterTable(TableVerifier.
    java:123)
    at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.populateFieldSQLTypeMap(RDB
    MSPersistenceManager.java:832)
    at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManag
    er.java:211)
    at
    weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
    at
    weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164)
    at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanIn
    foImpl.java:1004)
    at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
    at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:606)
    at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContain
    er.java:3007)
    at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2071)
    at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2052)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
    eContainer(SlaveDeployer.java:2558)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDe
    ployer.java:2483)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
    a:2308)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
    loyer.java:2390)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
    va:2302)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2455)
    at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:538)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:496)
    at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    Unable to deploy EJB: MessageRecord from macausms-ejb.jar:
    [EJB:011032]The container was unable to determine the java.sql.Types of
    database columns.
    weblogic.ejb20.WLDeploymentException: [EJB:011031]The Entity EJB requires
    the table: chk_messagerecord to be accessible. Please ensure that thistable
    exists and is accessible.
    at weblogic.ejb20.utils.TableVerifier.verifyTable(TableVerifier.java:242)
    at
    weblogic.ejb20.utils.TableVerifier.verifyOrCreateOrAlterTable(TableVerifier.
    java:123)
    at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.populateFieldSQLTypeMap(RDB
    MSPersistenceManager.java:832)
    at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManag
    er.java:211)
    at
    weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
    at
    weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164)
    at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanIn
    foImpl.java:1004)
    at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
    at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:606)
    at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContain
    er.java:3007)
    at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2071)
    at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2052)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
    eContainer(SlaveDeployer.java:2558)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDe
    ployer.java:2483)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
    a:2308)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
    loyer.java:2390)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
    va:2302)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2455)
    at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:538)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:496)
    at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1379)
    at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:606)
    at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContain
    er.java:3007)
    at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2071)
    at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
    a:2052)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
    eContainer(SlaveDeployer.java:2558)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDe
    ployer.java:2483)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
    a:2308)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
    loyer.java:2390)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
    va:2302)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2455)
    at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:538)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:496)
    at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    ==========================
    If you know what you are doing,
    it is not called RESEARCH!
    ==========================
    ==========================
    If you know what you are doing,
    it is not called RESEARCH!
    ==========================

  • JMS Adapter configuration failed in creating table that handles OEMS JM

    Step 2 from Chapter 8 of E15763-01, Oracle Application Integration Architecture -
    Foundation Pack 2.5: Integration Developer's
    Guide
    Configuring of JMS Adapters
    Create the table that handles the OEMS JMS destination (queue).
    Queues use a queue table. This SQL example creates a single table, AIA
    SALESORDERJMSQTAB, for a queue. The multiple_consumers parameter specifies
    whether there are multiple consumers. Set multiple_consumers to false for a queue.
    Begin
    DBMS_AQADM.CREATE_QUEUE_TABLE(Queue_table
    'AIA_SALESORDERJMSQTAB',Queue_payload_type 'SYS.AQ$_JMS_MESSAGE',
    sort_list 'PRIORITY,ENQ_TIME', multiple_consumers = >false,
    compatible '8.1.5');
    End;
    Result:
    SQL> Begin
    DBMS_AQADM.CREATE_QUEUE_TABLE(Queue_table
    'AIA_SALESORDERJMSQTAB',Queue_payload_type 'SYS.AQ$_JMS_MESSAGE',
    sort_list 'PRIORITY,ENQ_TIME', multiple_consumers = >false,
    compatible '8.1.5');
    End; 2 3 4 5 6
    SELECT * FROM ALL_TABLES WHERE TABLE_NAME='DBMS_AQADM.CREATE_QUEUE_TABLE';
    no rows selected

    Step 2 from Chapter 8 of E15763-01, Oracle Application Integration Architecture -
    Foundation Pack 2.5: Integration Developer's
    Guide
    Configuring of JMS Adapters
    Create the table that handles the OEMS JMS destination (queue).
    Queues use a queue table. This SQL example creates a single table, AIA
    SALESORDERJMSQTAB, for a queue. The multiple_consumers parameter specifies
    whether there are multiple consumers. Set multiple_consumers to false for a queue.
    Begin
    DBMS_AQADM.CREATE_QUEUE_TABLE(Queue_table
    'AIA_SALESORDERJMSQTAB',Queue_payload_type 'SYS.AQ$_JMS_MESSAGE',
    sort_list 'PRIORITY,ENQ_TIME', multiple_consumers = >false,
    compatible '8.1.5');
    End;
    Result:
    SQL> Begin
    DBMS_AQADM.CREATE_QUEUE_TABLE(Queue_table
    'AIA_SALESORDERJMSQTAB',Queue_payload_type 'SYS.AQ$_JMS_MESSAGE',
    sort_list 'PRIORITY,ENQ_TIME', multiple_consumers = >false,
    compatible '8.1.5');
    End; 2 3 4 5 6
    SELECT * FROM ALL_TABLES WHERE TABLE_NAME='DBMS_AQADM.CREATE_QUEUE_TABLE';
    no rows selected

  • Oracle 11g R2, CREATE TABLE and QUOTAS

    Hello everyone,
    I need some insight about a strange behavior I found out in Oracle 11gR2. Don't know if I do miss something or if I just found out a security issue with Oracle.
    Oracle Version : 11.2.0.1.0
    The problem is related with the CREATE TABLE privilege and the QUOTA on specific tablespace.
    Please, try this on your systems (if you have some spare time and care to confirm the "bug").
    Create a user, grant only two privileges, CREATE SESSION and CREATE TABLE.
    Grant NO quota on any tablespace.
    Try to create table on any tablespace (except SYSTEM) and tell everyone if it worked or not.
    The oracle documentation states the following :
    To create a relational table in your own schema, you must have the CREATE TABLE system privilege. To create a table in another user's schema, you must have the CREATE ANY TABLE system privilege. Also, the owner of the schema to contain the table must have either space quota on the tablespace to contain the table or the UNLIMITED TABLESPACE system privilege.
    [http://download.oracle.com/docs/cd/E11882_01/server.112/e17118/statements_7002.htm#SQLRF01402]
    The fact is, so far, on two different instances of Oracle 11gR2, my users are not limited in creating tables only where they have quotas but wherever they want except SYSTEM.
    The correct behavior would be to deny the table creation on tablespace where there is no quota but it does not.
    My instance of Oracle 10g are behaving correctly and thus the table creation is denied on tablespace with no quota.
    P.S1 Sorry if this a well known "bug/problem/issue". I've been ridicule on a well known forum for asking the same question. I am in no need to be "spoon filled" as stated on that famous website! I have read the documentation! I have googled a lot!
    P.S2 Even though the table creation work on tablespace with no quota, you still can't insert data in it. So, big picture, the user can't filled the tablespace with irrelevant data but he can creates thousand of tables...!
    Do I miss something?
    Is there any "default" option I have to flag to prevent table creation where it should not?
    ?(?)

    Hi. I'm planning on taking my OCP exam. If the exam ask a question realted to this topic, what is the correct answer?
    create user barry identified barry
    grant create session, create table to barry
    1) barry cannot create a table since he has no quota
    2) barry can create a table
    According to the oracle document, the barry needs quota on the tablespace to create a table. however, according to the link you provided, in 11gR2, barry does not need quota to create a table. He only needs a quota to insert data.

  • Drop and recreate table in stored procedure

    Hi all
    When creating tables using Transact-SQL scripts, I have always preferred to drop the table if it exists and then create it explicitly using CREATE TABLE.  For two reasons:
    1) It does not matter if it is the first time the SP is run ie. if I create the table manually in the first instance and just use TRUNCATE TABLE it could fail if the table is deleted
    2) I have control over the data types of the table fields
    Just recently though I discovered the error that can occur when dropping and creating a table in the same batch (see link below)
    Microsoft Website
    This causes me a problem when dropping and creating tables in stored procedures, as I understand that a stored procedure is in itself a single batch?
    Can I avoid this error in a stored procedure whilst continuing to drop and create tables?  Or should I be taking a different approach?
    Coding best practice advice would be greatly appreciated.
    Thank you

    Thanks Ronen
    Please see my second post immediately before your reply.
    Given that I need to store the data output in a physical table for use in QlikView, would you suggest truncating the table each time the SP runs?  And then having a script that handles both dropping and creating the physical table, and also creating
    the SP?
    >> QlikView
    QlikView is an Israeli company, right?
    In any case I am not familiar with QlikView's application, therefore I can only give you general information, based on assumptions regarding the application, and facts regarding the SQL Server.
    >> for use in QlikView
    I assume that external application use specific database structure (table
    structure) and it is change only in rare situations (for example CMS interface might change the tables if and when a module s update/install). In this case there is no need to drop the table and recreate it and TRUNCATE is the solution.
    >> would you suggest truncating the table each time the SP runs
    I am sorry but i cant recommend on TRUNCATE a table each time you execute SP, without know the exact reason for this logic. It sound to me, at this point of time (with the information that we have), that this
    is very bad logic (application architecture). As I wrote above, basing your application on TRUNCATING the table each time mean that you have problems with multi users. Thins about 2 people that try to execute the same SP at almost the same time. Think about
    locking in the SQL Server and bad data (one truncate while the other already inserted the new data and get no rows, if there is no locking).
    But TRUNCATE is much better in this case probably then DROP and DELETE, since it is faster, and locking will be shorter (hopefully the application use the correct locking). There are other reasons why TRUNCATE is better, and other people already mentioned
    most of them, but time in this scenario might be critical.
    >> having a script that handles both dropping and creating the physical table, and also creating the SP?
    I do not undestand what is this second step. we said that you truncate the table, so why do you need to
    dropping and creating the physical table and who
    creating the SP?
    Are you meaning that the application create the tables and SP?
    There are lot of application that during installation create the database structure. is this what you mean?
      Ronen Ariely
     [Personal Site]    [Blog]    [Facebook]

  • Create table of type integer

    How can we create a table of type integer in MDM. (what the code should be?)
    When I create a table, it only allows type Text.
    Thanks

    Hi R.N,
    we can create table of type Flat, Hierarachy, Taxanomy, Qualified Flat and Families.
    you are talking about field, by default whenever you create any table a field "Name" of type Text get generated, but here if you want this field to be integer, just create new field by right clickin "Add Field" by going into table in which you want that field. here you can give any name to that field and select type Integer . if you want only Integer field into your table then also make it "Display Field" only after that you can delete field "Name" of type Text.
    Note: For creating Table Click on your repository where you can see and create tables and for field just click on any table where you want to include that field into table
    Code takes important incase of Java APis and ABAP Apis. where APIs recognise table and fields with their code only.
    Remember to unload repository before creating Table and Fields and then load it.
    Hope it helps you,
    Mandeep Saini
    Edited by: Mandeep Saini on May 6, 2008 10:43 AM
    Edited by: Mandeep Saini on May 6, 2008 10:48 AM

  • Need Answer with Create Table

    Hi OTN Peeps,
    I would like to ask, what's the difference between this two syntax.
    create table table_name as
    select * from other_table;and
    create table table_name as
    (select * from other_table);Thanks and More Power!

    Hi,
    Cloud Nines Bliss wrote:
    Hi OTN Peeps,
    I would like to ask, what's the difference between this two syntax.
    create table table_name as
    select * from other_table;and
    create table table_name as
    (select * from other_table);
    There's no difference. Oracle often allows parentheses when they're not needed. For example:
    SELECT  SYSDATE - (1 / 24)    AS one_hour_ago
    FROM    dual;The results would be the same if you lost the parentheses, but it's nice to have them in this case, to make it clear that the / operation is being doen before the -.

  • Difference between an XMLType table and a table with an XMLType column?

    Hi all,
    Still trying to get my mind around all this XML stuff.
    Can someone concisely explain the difference between:
    create table this_is_xmltype_tab of xmltype;and
    create table this_is_tab_w_xmltpe_col(id number, document xmltype);What are the relative advantages and disadvantages of each approach? How do they really differ?
    Thanks,
    -Mark

    There is another pointer Mark, that I realized when I was thinking about the differences...
    If you would look up in the manual regarding "xdb:annotations" you would learn about a method using an XML Schema to generate out of the box your whole design in terms of physical layout and/or design principles. In my mind this should be the preferred solution if you are dealing with very complex XML Schema environments. Taking your XML Schema as your single point design layout, that during the actual implementation automatically generates and builds all your needed database objects and its physical requirements, has great advantages in points of design version management etc., but...
    ...it will create automatically an XMLType table (based on OR, Binary XML of "hybrid" storage principles, aka the ones that are XML Schema driven) and not AFAIK a XMLtype column structure: so as in "our" case a table with a id column and a xmltype column.
    In principle you could relationally relate to this as:
    +"I have created an EER diagram and a Physical diagram, I mix the content/info of those two into one diagram." "Then I _+execute+_ it in the database and the end result will be an database user/schema that has all the xxxx amount of physical objects I need, the way I want it to be...".+
    ...but it will be in the form of an XMLType table structure...
    xdb:annotations can be used to create things like:
    - enforce database/company naming conventions
    - DOM validation enabled or not
    - automatic IOT or BTree index creation (for instance in OR XMLType storage)
    - sort search order enforced or not
    - default tablenames and owners
    - extra column or table property settings like for partitioning XML data
    - database encoding/mapping used for SQL and binary storage
    - avoid automatic creation of Oracle objects (tables/types/etc), for instance, via xdb:defaultTable="" annotations
    - etc...
    See here for more info: http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10492/xdb05sto.htm#ADXDB4519
    and / or for more detailed info:
    http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10492/xdb05sto.htm#i1030452
    http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10492/xdb05sto.htm#i1030995
    http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10492/xdb05sto.htm#CHDCEBAG
    ...

  • ORA-39080: failed to create queues "" and "" for Data Pump job

    When I am running datapump expdp I receive the following error:
    +++Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc+++
    +++tion+++
    +++With the Partitioning, OLAP and Data Mining options+++
    +++ORA-31626: job does not exist+++
    +++ORA-31637: cannot create job SYS_EXPORT_SCHEMA_01 for user CHESHIRE_POLICE_LOCAL+++
    +++ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95+++
    +++ORA-06512: at "SYS.KUPV$FT_INT", line 600+++
    +++ORA-39080: failed to create queues "" and "" for Data Pump job+++
    +++ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95+++
    +++ORA-06512: at "SYS.KUPC$QUE_INT", line 1555+++
    +++ORA-01403: no data found+++
    Sys has the following two objects as invalid at present after running catproc.sql and utlrp.sql and manual compilation:
    OBJECT_NAME OBJECT_TYPE
    AQ$_KUPC$DATAPUMP_QUETAB_E QUEUE
    SCHEDULER$_JOBQ QUEUE
    While I run catdpb.sql the datapump queue table does not create:
    BEGIN
    dbms_aqadm.create_queue_table(queue_table => 'SYS.KUPC$DATAPUMP_QUETAB', multiple_consumers => TRUE, queue_payload_type =>'SYS.KUPC$_MESSAGE', comment => 'DataPump Queue Table', compatible=>'8.1.3');
    EXCEPTION
    WHEN OTHERS THEN
    IF SQLCODE = -24001 THEN NULL;
    ELSE RAISE;
    END IF;
    END;
    ERROR at line 1:
    ORA-01403: no data found
    ORA-06512: at line 7

    Snehashish Ghosh wrote:
    When I am running datapump expdp I receive the following error:
    +++Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc+++
    +++tion+++
    +++With the Partitioning, OLAP and Data Mining options+++
    +++ORA-31626: job does not exist+++
    +++ORA-31637: cannot create job SYS_EXPORT_SCHEMA_01 for user CHESHIRE_POLICE_LOCAL+++
    +++ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95+++
    +++ORA-06512: at "SYS.KUPV$FT_INT", line 600+++
    +++ORA-39080: failed to create queues "" and "" for Data Pump job+++
    +++ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95+++
    +++ORA-06512: at "SYS.KUPC$QUE_INT", line 1555+++
    +++ORA-01403: no data found+++
    Sys has the following two objects as invalid at present after running catproc.sql and utlrp.sql and manual compilation:
    OBJECT_NAME OBJECT_TYPE
    AQ$_KUPC$DATAPUMP_QUETAB_E QUEUE
    SCHEDULER$_JOBQ QUEUE
    While I run catdpb.sql the datapump queue table does not create:
    BEGIN
    dbms_aqadm.create_queue_table(queue_table => 'SYS.KUPC$DATAPUMP_QUETAB', multiple_consumers => TRUE, queue_payload_type =>'SYS.KUPC$_MESSAGE', comment => 'DataPump Queue Table', compatible=>'8.1.3');does it work better when specifying an Oracle version that is from this Century; newer than V8.1?

Maybe you are looking for