LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only

  • 1.  Direct Path Context Error writing to database using DB Store node

    Employee
    Posted 06-05-2014 10:37

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: prashanth

    I see this error sometimes when data is attempted to be written to the table using the DB Store node.

    I don't think this is a space issue although we have been having some.

    Here is the error log:

    Errors for Load_Record_Type_Table
    ERROR initializing expert output:
    Error preparing direct path context
    2014-06-05 15:52:27.000; WARN: type: 1 size: 25 col: 0
    id: 0 chain: 0 group: 0
    cppDetail: context: OciDPLoaderContext::setColumnSize() build/linux-x86-64/release/code/source/jigsaw/db/oci/OciDPLoaderContext.cpp@398

    2014-06-05 15:52:27.000; WARN: type: 1 size: 50 col: 1
    id: 0 chain: 0 group: 0
    cppDetail: context: OciDPLoaderContext::setColumnSize() build/linux-x86-64/release/code/source/jigsaw/db/oci/OciDPLoaderContext.cpp@398

    2014-06-05 15:52:27.000; WARN: type: 1 size: 15 col: 2
    id: 0 chain: 0 group: 0
    cppDetail: context: OciDPLoaderContext::setColumnSize() build/linux-x86-64/release/code/source/jigsaw/db/oci/OciDPLoaderContext.cpp@398

    2014-06-05 15:52:27.000; WARN: type: 1 size: 20 col: 3
    id: 0 chain: 0 group: 0
    cppDetail: context: OciDPLoaderContext::setColumnSize() build/linux-x86-64/release/code/source/jigsaw/db/oci/OciDPLoaderContext.cpp@398

    .....

    2014-06-05 15:52:57.000; WARN: OCI Error 604: ORA-00604: error occurred at recursive SQL level 1
    ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired

    id: 0 chain: 0 group: 0
    cppDetail: context: build/linux-x86-64/release/code/source/jigsaw/db/oci/OciUtils.cpp@83

    2014-06-05 15:52:57.000; WARN: Error preparing direct path context
    id: 0 chain: 0 group: 0
    cppDetail: context: OciDPLoaderContext::CreateLoader() build/linux-x86-64/release/code/source/jigsaw/db/oci/OciDPLoaderContext.cpp@805

    2014-06-05 15:52:57.000; WARN: Error creating loader
    id: 0 chain: 0 group: 0
    cppDetail: context: DBTableOutput::initializeLoader() build/linux-x86-64/release/code/source/brain/io/DBTableOutput.cpp@776

    2014-06-05 15:52:57.000; WARN: ...handling expression #1 in file
    id: 0 chain: 0 group: 0
    cppDetail: context: Salmon::NED::ExprTableIo::initialize() build/linux-x86-64/release/code/source/brain/node/ExprTableIo.cpp@86

    2014-06-05 15:52:57.000; WARN: ...exception seen
    id: 0 chain: 0 group: 0
    cppDetail: context: Salmon::NED::NodeControl::initializeExpert() build/linux-x86-64/release/code/source/brain/node/NodeControl.cpp@1331

    2014-06-05 15:52:57.000; ERROR: ERROR initializing expert output:
    Error preparing direct path context
    id: 0 chain: 0 group: 0
    cppDetail: context: Salmon::NED::NodeMain::errorMsg() build/linux-x86-64/release/code/source/brain/node/NodeMain.cpp@28


  • 2.  RE: Direct Path Context Error writing to database using DB Store node

    Employee
    Posted 06-05-2014 11:11

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ejones

    I have not seen this issue but often, with Oracle, you can search the Internet error code numbers as key words. I think that this may be an issue where the Oracle DBA will be needed.

    You might try what is suggested here, https://community.oracle.com/thread/...art=0&tstart=0 since there is a parameter in the Optional tab for IndexMaintenance and you can set it to skipUnusable.

    And this page provides some other ideas, http://nimishgarg.blogspot.com/2012/...d-acquire.html
    How to avoid the ORA-00054:
    - Execute DDL at off-peak hours, when database is idle.
    - Execute DDL in maintenance window.
    - Find and Kill the session that is preventing the exclusive lock.
    And one of the solutions that it lists which we might be able to do from LAE is the following, but replacing the object name with the object you are attempting to lock. Before killing the process you might try additional queries in the system tables to find at least the username if not part of the SQL statement that is locking the table.
    Solution 4:

    Step 1: Identify the session which is locking the object
    select a.sid, a.serial#
    from v$session a, v$locked_object b, dba_objects c
    where b.object_id = c.object_id
    and a.sid = b.session_id
    and OBJECT_NAME='EMP';

    Step 2: kill that session using
    alter system kill session 'sid,serial#';


  • 3.  RE: Direct Path Context Error writing to database using DB Store node

    Employee
    Posted 06-05-2014 11:11

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: stonysmith

    I think basically, this means that someone else has the record or table locked, and you aren't allowed to make changes at this time.


  • 4.  RE: Direct Path Context Error writing to database using DB Store node

    Employee
    Posted 06-05-2014 12:35

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: prashanth

    Originally posted by: stonysmith
					

    I think basically, this means that someone else has the record or table locked, and you aren't allowed to make changes at this time.

    Correct. I disconnected from the database on SQL Developer which committed changes (not sure if there were any). This fixed the issue.