Oracle timestamp to unix timestamp

Hi everyone!
I need to convert a values fetched from a db table in a unix timestamp (seconds passed by january first 1970).
The table is like this
create table test(.... ts timestamp not null...);
and the code to define the output variable (for a select statement) is the following, where time is an OCIDateTime variable
OCIDefineByPos(stmth, &defineh, errh, pos, (dvoid *) time, 0, SQLT_ODT,
(dvoid *) 0, (ub2 *) 0, (ub2 *) 0, OCI_DEFAULT);
once I have initialized "time", how can I convert his content to unix timestamp?
And viceversa, how can I put an int value rapresenting a unix timestamp in an OCIDateTime variable, and then insert it correctly inside mt table?
thank you!
GePs

I define my buffer according on the the table's field width I retrieve from metadata. In ths way:
OCIAttrGet((dvoid *) pars, (ub4) OCI_DTYPE_PARAM, (dvoid *) col_width, (ub4 *) 0,
(ub4) OCI_ATTR_DATA_SIZE, (OCIError *) err);
Now in col_width there's the dimension of the field (for a timestamp field is 11!). Then I bind the correct variable in the correct manner (with a varchar2 fiedl it works!)
int pos = 1;
char *time;
time = malloc(sizeof(char*));
OCIDefineByPos(stmt, defs, err, (ub4) pos, time, (sword) col_width+ 1, SQLT_STR, (dvoid *) 0,
                              (ub2 *)0, (ub2 *)0, OCI_DEFAULT);
Now if I print time I get the trunked timestamp
printf("%s", time); //-> 11-NOV-05 1

Similar Messages

  • Unix timestamp to Oracle timestamp conversion

    Hi all,
    I am trying to convert the UNIX timestamp to ORACLE timestamp .
    I have done like this upto now.
    CREATE OR REPLCACE FUNCTION unixts_to_oraclets(unixtimestamp IN INTEGER)
    RETURN DATE IS
    result DATE;
    BEGIN
    result := TO_DATE('1970-01-01', 'YYYY-MM-DD') + numtodsinterval(unixtimestamp, 'SECOND');
    return(result);
    end unixts_to_oraclets;
    now i have run this query
    SQL> select unixts_to_oraclets(1139291114) as TS from dual;
    TS
    07-FEB-06
    now i need the ouput to like this 07-FEB-06 01:10:12
    for that i have done like this:
    DECLARE
    v_date DATE;
    res_date DATE;
    BEGIN
    SELECT from_uts(1139291114)INTO v_date FROM dual;
    SELECT TO_TIMESTAMP(v_date,'DD-MON-RRHH24.MI.SS.FF') INTO res_date FROM dual;
    DBMS_OUTPUT.PUT_LINE(res_date);
    END;
    but the output is :
    SQL> /
    07-FEB-06
    PL/SQL procedure successfully completed.
    why is that it is not printing 07-FEB-06 01:10:12 ?
    how should i moodify the code to get the desired output.
    please help me i this regard
    Trinath Somanchi,
    Hyderabad.

    SQL> exec dbms_output.put_line(sysdate);
    07-FEB-06
    PL/SQL procedure successfully completed.
    SQL> exec dbms_output.put_line(to_char(sysdate, 'DD-MM-YYYY HH24:MI:SS'));
    07-02-2006 02:48:35
    PL/SQL procedure successfully completed.
    SQL> alter session set nls_date_format='DD-MM-YYYY HH24:MI:SS';
    Session altered.
    SQL> exec dbms_output.put_line(sysdate);
    07-02-2006 02:49:03
    PL/SQL procedure successfully completed.

  • Mapping util.Date to Oracle timestamp

    Tuesday, March 22, 2005
    I am currently experiencing difficulty in mapping a java.util.Date
    field to an Oracle TIMESTAMP column.
    Here's what I see. By default, Kodo maps the date field to a DATE
    column. I suppose this makes sense since Oracle's date columns
    have time information that resolves to the second. In this case,
    the client has a business case to store subsecond resolution,
    hence the desire to store the date field in an Oracle TIMESTAMP
    column.
    First question: how should this be done?
    Here's what I've tried. I tried setting the jdbc-type extension
    for the date field to "timestamp". This setting makes no
    difference, and I suspect the reason is that OracleDBDictionary
    has made the mapping from TIMESTAMP to DATE.
    I tried setting the jdbc-sql-type extension for the date field to
    "timestamp". This makes a difference only when I drop the table.
    Then the schematool's refresh action creates a table with date's
    field mapped to a TIMESTAMP column. I have also gone ahead and
    manually altered the table to achieve the same effect.
    Once the mapping is created, I see the following behavior. Kodo
    has no problem reading the TIMESTAMP column and putting the info
    into the date field. It also has no problem saving non-null date
    values into the TIMESTAMP column. But it does have a problem
    storing a null in the date field.
    Second question: what is the workaround to this problem?
    The the stack dump (obtained by using the JDO Tools Library
    example) follows.
    Thanks in advance,
    David Ezzio
    enter command:
    --> return book
    Select the book to return:
    1. book [com.ysoft.jdo.book.library.Book-354] "Gone to War" checked out:
    Tue Mar 22 10:38:01 EST 2005
    2. book [com.ysoft.jdo.book.library.Book-356] "Gone to Work" checked
    out: Tue Mar 22 10:33:58 EST 2005
    3. book [com.ysoft.jdo.book.library.Book-357] "Gone Fishing" checked
    out: Tue Mar 22 10:33:58 EST 2005
    4. book [com.ysoft.jdo.book.library.Book-360] "Gone Sailing" checked
    out: Tue Mar 22 10:33:58 EST 2005
    5. book [com.ysoft.jdo.book.library.Book-355] "Gone Hunting" checked
    out: Tue Mar 22 10:33:58 EST 2005
    Enter selection:
    --> 2
    okay
    enter command:
    --> commit
    exception caught in command
    kodo.util.FatalDataStoreException: The transaction has been rolled back.
    See the nested exceptions for details on the errors that occu
    rred.
    at
    kodo.runtime.PersistenceManagerImpl.throwFlushException(PersistenceManagerImpl.java:1262)
    at
    kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1122)
    at
    kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1005)
    at
    kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:932)
    at
    kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
    at
    kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:592)
    at
    com.ysoft.jdo.book.library.LibraryHandler.commitTransaction(LibraryHandler.java:175)
    at
    com.ysoft.jdo.book.library.client.CommitTransaction.execute(Library.java:279)
    at
    com.ysoft.jdo.book.common.console.UserInterface.execute(UserInterface.java:196)
    at
    com.ysoft.jdo.book.common.console.UserInterface.pumpCommands(UserInterface.java:186)
    at com.ysoft.jdo.book.library.client.Library.run(Library.java:139)
    at com.ysoft.jdo.book.library.client.Library.main(Library.java:104)
    NestedThrowablesStackTrace:
    kodo.util.DataStoreException: Invalid column type
    at
    kodo.jdbc.sql.DBDictionary.newDataStoreException(DBDictionary.java:3081)
    at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:77)
    at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:63)
    at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:43)
    at
    kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:89)
    at
    kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:445)
    at
    kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:193)
    at
    kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:95)
    at
    kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:609)
    at
    kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:153)
    at
    kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1122)
    at
    kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1005)
    at
    kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:932)
    at
    kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
    at
    kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:592)
    at
    com.ysoft.jdo.book.library.LibraryHandler.commitTransaction(LibraryHandler.java:175)
    at
    com.ysoft.jdo.book.library.client.CommitTransaction.execute(Library.java:279)
    at
    com.ysoft.jdo.book.common.console.UserInterface.execute(UserInterface.java:196)
    at
    com.ysoft.jdo.book.common.console.UserInterface.pumpCommands(UserInterface.java:186)
    at com.ysoft.jdo.book.library.client.Library.run(Library.java:139)
    at com.ysoft.jdo.book.library.client.Library.main(Library.java:104)
    NestedThrowablesStackTrace:
    java.sql.SQLException: Invalid column type
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
    at
    oracle.jdbc.driver.OracleStatement.get_internal_type(OracleStatement.java:6164)
    at
    oracle.jdbc.driver.OraclePreparedStatement.setNull(OraclePreparedStatement.java:1316)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
    at
    com.solarmetric.jdbc.PoolConnection$PoolPreparedStatement.setNull(PoolConnection.java:406)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
    at
    com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.setNull(LoggingConnectionDecorato
    r.java:792)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
    at kodo.jdbc.sql.DBDictionary.setNull(DBDictionary.java:950)
    at
    kodo.jdbc.sql.OracleDictionary.setNull(OracleDictionary.java:450)
    at kodo.jdbc.sql.RowImpl.toSQL(RowImpl.java:828)
    at kodo.jdbc.sql.RowImpl.flush(RowImpl.java:1039)
    at kodo.jdbc.sql.RowImpl.flush(RowImpl.java:975)
    at
    kodo.jdbc.runtime.PreparedStatementManager.flushInternal(PreparedStatementManager.java:160)
    at
    kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:84)
    at
    kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:445)
    at
    kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:193)
    at
    kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:95)
    at
    kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:609)
    at
    kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:153)
    at
    kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1122)
    at
    kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1005)
    at
    kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:932)
    at
    kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
    at
    kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:592)
    at
    com.ysoft.jdo.book.library.LibraryHandler.commitTransaction(LibraryHandler.java:175)
    at
    com.ysoft.jdo.book.library.client.CommitTransaction.execute(Library.java:279)
    at
    com.ysoft.jdo.book.common.console.UserInterface.execute(UserInterface.java:196)
    at
    com.ysoft.jdo.book.common.console.UserInterface.pumpCommands(UserInterface.java:186)
    at com.ysoft.jdo.book.library.client.Library.run(Library.java:139)
    at com.ysoft.jdo.book.library.client.Library.main(Library.java:104)
    enter command:
    -->

    Hi Stephen,
    There are two related issues that are addressed. One, some Oracle
    drivers return the wrong type (Type.OTHER) for the TIMESTAMP field.
    This is true for the
    9.2.0.1.0 driver that ships with 9iR2. This causes an exception when
    attempting to assign a null to the date field that has been mapped to a
    TIMESTAMP column. Two, all of the 9i drivers (and 10g drivers) return a
    type name of "TIMESTAMP(x)" where x is the precision. This confuses
    Kodo's OracleDictionary which is looking for a string without the
    precision characters.
    Following your suggestion, the following code fixes it just fine. It is
    harmless, in that all it does is do what OracleDictionary intended but
    failed to do. To use it, you must add the following property
    configuration to the kodo.properties file.
    kodo.jdbc.DBDictionary: xxx.jdo.FixedOracleDictionary
    Without the fix, Kodo does not reassign the TIMESTAMP columns to a type
    of DATE. So far as I can tell, as long as the driver returns a
    Types.TIMESTAMP this does not cause a failure.
    This fix will be moot as soon as the bug in OracleDictionary is fixed.
    What I wonder about is why does Kodo reassign type TIMESTAMP to DATE?
    Why don't you treat TIMESTAMP types as TIMESTAMP types? Curious minds
    want to know.
    Best wishes,
    David
    ---- code follows
    package xxx.jdo;
    import java.sql.*;
    import kodo.jdbc.schema.*;
    import kodo.jdbc.sql.*;
    * Some Oracle drivers do not return the correct type for the TIMESTAMP
    field.
    * This class fixes this issue for Kodo 3.3. The problem (an exception
    complaining
    * about an invalid column type) appears when mapping a Java field
    (Date for example) to
    * an Oracle timestamp field, and only when attempting to set null on
    the Java field.
    public class FixedOracleDictionary
    extends OracleDictionary
    public Column[] getColumns (DatabaseMetaData meta, String catalog,
    String schemaName, String tableName,
    String columnName, Connection conn)
    throws SQLException
    // Let Kodo's OracleDictionary do its thing
    Column[] cols = super.getColumns (meta, catalog, schemaName,
    tableName,
    columnName, conn);
    // Catch the columns with a name of "TIMESTAMP(n)" and mark them
    as DATE types.
    // This is what the OracleDictionary intended to do, but was
    foiled by the
    // name which now has a precision.
    for (int i = 0; cols != null && i < cols.length; i++)
    String tName = cols.getTypeName();
    if (tName != null && tName.startsWith("TIMESTAMP"))
    cols[i].setType(Types.DATE);
    return cols;
    ---- code ends
    Stephen Kim wrote:
    This is a bug (1111)with regards to specific combinations of Oracle 10
    driver and db.
    To work around the issue until the next relase, getColumns (...) in
    OracleDictionary needs to be extended/modified to instead of doing a
    strict equals () comparison to "TIMESTAMP", to instead do a startsWith
    ("TIMESTAMP")
    David Ezzio wrote:
    Tuesday, March 22, 2005
    I am currently experiencing difficulty in mapping a java.util.Date
    field to an Oracle TIMESTAMP column.
    Here's what I see. By default, Kodo maps the date field to a DATE
    column. I suppose this makes sense since Oracle's date columns
    have time information that resolves to the second. In this case,
    the client has a business case to store subsecond resolution,
    hence the desire to store the date field in an Oracle TIMESTAMP
    column.
    First question: how should this be done?
    Here's what I've tried. I tried setting the jdbc-type extension
    for the date field to "timestamp". This setting makes no
    difference, and I suspect the reason is that OracleDBDictionary
    has made the mapping from TIMESTAMP to DATE.
    I tried setting the jdbc-sql-type extension for the date field to
    "timestamp". This makes a difference only when I drop the table.
    Then the schematool's refresh action creates a table with date's
    field mapped to a TIMESTAMP column. I have also gone ahead and
    manually altered the table to achieve the same effect.
    Once the mapping is created, I see the following behavior. Kodo
    has no problem reading the TIMESTAMP column and putting the info
    into the date field. It also has no problem saving non-null date
    values into the TIMESTAMP column. But it does have a problem
    storing a null in the date field.
    Second question: what is the workaround to this problem?
    The the stack dump (obtained by using the JDO Tools Library
    example) follows.
    Thanks in advance,
    David Ezzio
    enter command:
    --> return book
    Select the book to return:
    1. book [com.ysoft.jdo.book.library.Book-354] "Gone to War" checked
    out:
    Tue Mar 22 10:38:01 EST 2005
    2. book [com.ysoft.jdo.book.library.Book-356] "Gone to Work" checked
    out: Tue Mar 22 10:33:58 EST 2005
    3. book [com.ysoft.jdo.book.library.Book-357] "Gone Fishing" checked
    out: Tue Mar 22 10:33:58 EST 2005
    4. book [com.ysoft.jdo.book.library.Book-360] "Gone Sailing" checked
    out: Tue Mar 22 10:33:58 EST 2005
    5. book [com.ysoft.jdo.book.library.Book-355] "Gone Hunting" checked
    out: Tue Mar 22 10:33:58 EST 2005
    Enter selection:
    --> 2
    okay
    enter command:
    --> commit
    exception caught in command
    kodo.util.FatalDataStoreException: The transaction has been rolled
    back. See the nested exceptions for details on the errors that occu
    rred.
    at
    kodo.runtime.PersistenceManagerImpl.throwFlushException(PersistenceManagerImpl.java:1262)
    at
    kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1122)
    at
    kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1005)
    at
    kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:932)
    at
    kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
    at
    kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:592)
    at
    com.ysoft.jdo.book.library.LibraryHandler.commitTransaction(LibraryHandler.java:175)
    at
    com.ysoft.jdo.book.library.client.CommitTransaction.execute(Library.java:279)
    at
    com.ysoft.jdo.book.common.console.UserInterface.execute(UserInterface.java:196)
    at
    com.ysoft.jdo.book.common.console.UserInterface.pumpCommands(UserInterface.java:186)
    at
    com.ysoft.jdo.book.library.client.Library.run(Library.java:139)
    at
    com.ysoft.jdo.book.library.client.Library.main(Library.java:104)
    NestedThrowablesStackTrace:
    kodo.util.DataStoreException: Invalid column type
    at
    kodo.jdbc.sql.DBDictionary.newDataStoreException(DBDictionary.java:3081)
    at
    kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:77)
    at
    kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:63)
    at
    kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:43)
    at
    kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:89)
    at
    kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:445)
    at
    kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:193)
    at
    kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:95)
    at
    kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:609)
    at
    kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:153)
    at
    kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1122)
    at
    kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1005)
    at
    kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:932)
    at
    kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
    at
    kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:592)
    at
    com.ysoft.jdo.book.library.LibraryHandler.commitTransaction(LibraryHandler.java:175)
    at
    com.ysoft.jdo.book.library.client.CommitTransaction.execute(Library.java:279)
    at
    com.ysoft.jdo.book.common.console.UserInterface.execute(UserInterface.java:196)
    at
    com.ysoft.jdo.book.common.console.UserInterface.pumpCommands(UserInterface.java:186)
    at
    com.ysoft.jdo.book.library.client.Library.run(Library.java:139)
    at
    com.ysoft.jdo.book.library.client.Library.main(Library.java:104)
    NestedThrowablesStackTrace:
    java.sql.SQLException: Invalid column type
    at
    oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
    at
    oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
    at
    oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
    at
    oracle.jdbc.driver.OracleStatement.get_internal_type(OracleStatement.java:6164)
    at
    oracle.jdbc.driver.OraclePreparedStatement.setNull(OraclePreparedStatement.java:1316)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
    at
    com.solarmetric.jdbc.PoolConnection$PoolPreparedStatement.setNull(PoolConnection.java:406)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
    at
    com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.setNull(LoggingConnectionDecorato
    r.java:792)
    at
    com.solarmetric.jdbc.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:369)
    at kodo.jdbc.sql.DBDictionary.setNull(DBDictionary.java:950)
    at
    kodo.jdbc.sql.OracleDictionary.setNull(OracleDictionary.java:450)
    at kodo.jdbc.sql.RowImpl.toSQL(RowImpl.java:828)
    at kodo.jdbc.sql.RowImpl.flush(RowImpl.java:1039)
    at kodo.jdbc.sql.RowImpl.flush(RowImpl.java:975)
    at
    kodo.jdbc.runtime.PreparedStatementManager.flushInternal(PreparedStatementManager.java:160)
    at
    kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:84)
    at
    kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:445)
    at
    kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:193)
    at
    kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:95)
    at
    kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:609)
    at
    kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:153)
    at
    kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1122)
    at
    kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1005)
    at
    kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:932)
    at
    kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
    at
    kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:592)
    at
    com.ysoft.jdo.book.library.LibraryHandler.commitTransaction(LibraryHandler.java:175)
    at
    com.ysoft.jdo.book.library.client.CommitTransaction.execute(Library.java:279)
    at
    com.ysoft.jdo.book.common.console.UserInterface.execute(UserInterface.java:196)
    at
    com.ysoft.jdo.book.common.console.UserInterface.pumpCommands(UserInterface.java:186)
    at
    com.ysoft.jdo.book.library.client.Library.run(Library.java:139)
    at
    com.ysoft.jdo.book.library.client.Library.main(Library.java:104)
    enter command:
    -->

  • How to convert oracle timestamp to java timestamp

    Hi,
    I need to convert oracle timestamp that i got from oracle database to java timestamp.I tried to use getTimestamp() to get timestamp value from oracle, but am getting NumberFormatException.
    Could any of suggest how to convert oracle timestamp to java timestamp.

    Thanks jverd ,
    then my code will be like:
    String oracleTS="11-MAR-05 11.19.20.625 AM";
    // am looking for yyyy-MM-dd HH:mm:ss format
    SimpleDateFormat sdf=new SimpleDateFormat("yyyy-MM-dd
    HH:mm:ss");           
    Timestamp javaTimestamp=Timestamp.valueOf(oracleTS);
    System.out.println("javaTimestamp----->>
    "+javaTimestamp);
    ving java.lang.NumberFormatException: For input
    string: "MAR"Well, the SimpleDateFormat has to actually match the format you're trying to parse, for one thing. Then you have to actually USE the SDF, which you didn't.
    You really haven't made it clear what you're trying to do, and it doesn't appear that you bothered to study the links I provided.
    DateFormat df = new SimpleDateFormat("dd-MMM-yy HH.mm.ss.SSS aa");
    Date date = df.parse(oracleTS);
    Timestamp ts = new Timestamp(date.getTime());

  • Converting Oracle TIMESTAMP(4) column to SQL datetime column conversion error in ssis

    I could not able to convert Oracle TIMESTAMP(4) column to SQL datetime column conversion error in ssis.
    I'm connecting OLEDD Oracle Source to OLEDB SQL Destination in SSIS package. I'm trying to insert data from oracle datetime column into sql datetime column. I'm getting some errors.
    Please provide helpful info.

    You can transform the data types directly at the source by writing a proper SQL statement, or you can convert them using the data conversion component.
    Please refer the below link
    http://stackoverflow.com/questions/6256168/how-to-convert-a-timestamp-in-string-format-to-datetime-data-type-within-a-packa

  • DB2 timestamp to oracle timestamp conversion

    Does any one know how to convert Db2 timestamp into oracle timestamp.
    From DB2 we are getting timestamp in this format (2000-03-06-16.02.19.074474) (26 bytes).
    I want to insert this into oracle thru owb into oracle table with column type timestamp.
    Does anyone know the procedure for this type of conversion
    Thanks in advance..

    Hi,
    Try a migration tool at www.ispirer.com/chyfo.html
    It provides you the fastest, the easiest and the most powerful way to migrate
    DB2 database into Oracle.
    It works in conjunction with Oracle SQL Loader. The tool creates text files (moving of LOBs are fully supported), generates
    CREATE TABLE scripts for Oracle and control files for SQL Loader.
    The tool has a lot of other features.
    Best regards, Dmitry.
    null

  • 10g Oracle Timestamp conversion to milliseconds

    Hello!
    I'm sure this is possible and I have found a couple of references but none that work.
    How can I take an Oracle Timestamp and convert it using a SELECT statement into milliseconds?
    Thanks in advance

    It looked interesting but I don't think it is the answer.
    Isn't the Oracle timestamp based on the elapsed seconds since some date in 1970 or something? It seems there should be an algorithm to convert but I just haven't found it.

  • ORACLE SERVER AND UNIX TP MONITOR-2

    제품 : ORACLE SERVER
    작성날짜 : 1995-01-24
    Subject: Oracle Server and UNIX Transaction Processing Monitors-2
    Page(3/4)
    This file contains commonly asked questions about Oracle7 Server and UNIX
    Transaction Processing Monitors (TPMs). The topics covered in this article are
         o Oracle Parallel Server and TP Monitors
         o Oracle and DCE-based TP Monitors
         o Other commonly asked questions
    The questions answered in part 3 provide additional detail to the information
    provided in part 1.
    Oracle Parallel Server and TP Monitors
    ======================================
    How does Oracle Parallel Server (OPS) work with TP Monitors?
    If you are using Oracle-managed transactions, there are no special
    considerations. But if you are using TPM-managed transactions, and
    thus need to use the XA interface, then Oracle requires release 7.1.3
    or later and a special version of the Distributed Lock Manager, called
    the session-based lock manager. This version of the DLM is not yet
    available for all platforms. To understand this restriction, let's take
    a look at one of the technical details of XA.
    The XA specification requires that the Resource Manager be able to
    move a transaction from one process to another, and even to be
    able to commit in a separate process. In Oracle, transactions are
    attached to sessions, so that means that we also have to be able to
    move sessions. Therefore, the session/transaction can't have any state
    which is tied to a particular process. The first generation distributed
    lock managers were all built to use the process id as the lock owner,
    which doesn't work for locks which need to move with the transaction.
    Oracle and DCE-based TP Monitors
    ================================
    How does Oracle interface to the Encina TP monitor? To CICS/6000? I've
    heard that they require OSF DCE facilities in order to run?
    Oracle interfaces to Encina and CICS/6000 just as it does to any other
    TP Monitor. The TP Monitor issues XA commands to control transactions, and
    Oracle executes the commands. Encina and CICS/6000 do use DCE features for
    their own operation. However, this use is transparent to the Oracle Server.
    What DCE facilities can Oracle products take advantage of when working with
    a DCE-based TP Monitor?
    The two most commonly mentioned DCE features which might be useful
    to Oracle users are multi-threading and security. We look at these in
    the subsequent questions in this section.
    Encina documentation suggests that a Resource Manager such as Oracle can
    be either single-threaded or multi-threaded? Which way is Oracle XA
    implemented?
    The Oracle XA implementation is single-threaded, as is any Oracle client.
    Within a single process, at most one thread can access Oracle at a time.
    Does that mean that only a single Encina application can access an instance
    of Oracle transactionally at any given moment?
    No. Oracle XA is only single-threaded within a single application server
    process. Multiple applications can access Oracle simultaneously using XA
    by using different application processes. Encina allows
    (1) serial reuse of a single server by different clients. There are
    two options for this. The server can use long term reservation
    but be defined to be in shared or concurrent access mode, which
    allows the server to be used by another client as soon as an RPC
    completes. Alternatively, the server can use default reservation
    and exclusive mode, which allows the server to be used by another
    client as soon as the current transaction ends.
    (2) concurrent execution by multiple servers, even if they are accessing
    the same Oracle database. These may be executing the same or different
    procedures.
    These two features should let you get as much concurrency as you need.
    Why isn't the Oracle XA library multi-threaded?
    The XA specification specifically states that its use of the phrase
    "thread of control" means a process. If an RM were to multi-thread its
    XA, it would be in violation of the specification. This restriction
    was put place in because at the time the specification was written,
    there were numerous thread packages: if the TM used one, the application
    another, and perhaps the RM yet a third, there's no way it could work.
    As threads standards settle down, the later versions of XA will probably
    relax this restriction.
    Will Oracle change if the XA specification changes?
    Very likely. The exact time frame will of course depend on the priority of
    all work items at that time.
    Does Oracle use DCE security via the TP Monitors?
    The integrity of the connection between a DCE TP Monitor client and DCE
    TP Monitor server is protected by the DCE security functionality.
    Theoretically, the TP Monitor could make the DCE-protected client security
    information available to Oracle. Unfortunately, there's no standard way
    for a TP Monitor to pass security information information to a Resource
    Manager such as Oracle. Oracle is leading an effort to extend the X/Open
    model to allow use of the security information provided by the Monitor.
    In the meantime, the basic DCE security features such as encryption are
    useful within TP Monitors.
    Effective use of DCE security would normally also mean that the security of
    the TP Monitor client be passed through the TP Monitor, through the Oracle
    client (application server), to the Oracle Server, and possibly on
    to other Oracle Servers through database links. The ability to transfer
    security information to other processes, called delegation, is missing
    in DCE version 1.0. DCE version 1.1, expected to emerge in late 1994,
    has some delegation features. Oracle is examining these features to see
    how they might be used.
    Are there any special considerations for CICS/6000?
    There are two:
    (1) It is inefficient to run without XA. CICS/6000 is designed to
    use XA. It uses XA so that the CICS server can log on to Oracle
    when it starts, after which it makes that Oracle connection available
    to any transaction it executes. If you don't use XA, the CICS server
    does not itself log on to Oracle so each transaction has to log on
    and log off - a very expensive mode of operation. Also, it is very
    un-cics-like in that the application does the log{on,off} and also
    commits - in a mainframe CICS database program CICS would implicitly
    do these operations. Oracle does not recommend this mode because of the
    performance penalty.
    (2) CICS servers are generic and dynamically load application modules.
    In order for these modules to access the Oracle connection made by
    CICS, the applications must be built with a shared object version of
    the Oracle libraries. This is an installation option on platforms which
    support CICS/6000 and other products using its architecture such as
    CICS 9000.
    Other commonly asked questions
    ==============================
    What other Resource Managers can be included in an Oracle XA transaction?
    Several other relational database vendors have an XA implementation
    available or in progress. There is an XA C-ISAM product from
    Gresham Telecomputing. There are also Resource Managers contained
    within some of the TP Monitors which can be coordinated in the same
    transaction. For example, CICS/6000 has VSAM files and other data
    stores, Encina has its RQS queuing system, and Tuxedo has its /Q queuing
    system.
    What is Recoverable Queuing Service (RQS) and how does it interoperate with
    Oracle7 and Encina? What about /Q?
    Recoverable Queuing Service is a feature provided by Encina which allows
    transactional, distributed queuing (enqueue/dequeue). Tuxedo has a similar
    product called /Q. Because these products are themselves coordinated by the
    TM component of the TP Monitor, their queue operations are atomically
    coordinated with with operations on XA Resource Managers such as Oracle7
    Server. That is, they can atomically put something on one of their queues
    and commit an Oracle transaction, then at some later time dequeue an
    entry atomically with doing some other Oracle transaction. The queue
    system guarantees that the message will not be lost or transmitted twice.
    Can I mix TP Monitor applications with standard Oracle7 Server applications?
    Yes, you can have existing Oracle applications connected to the database
    with alongside TPM applications against the same database. The TPM does
    not manage the whole database, just those transactions which are started
    by the TPM. The Oracle Server will properly handle concurrency control
    between the transactions managed by itself and those managed by the TPM.
    Is Oracle planning to change its tools to be more suitable for TP Monitors?
    With Oracle Procedure Builder 1.5, to be available with CDE2,
    Oracle will provide a foreign function interface that allows you to
    dynamically set up PL/SQL calls that access C functions. In other
    words, you can access C routines in Windows DLLs from within your
    PL/SQL procedures. This will allow PL/SQL under Windows easy access to
    TP Monitor APIs.
    Does Oracle7 Server itself use XA-compliant TPMs as the interface to
    foreign RMs?
    No, for this purpose Oracle Server uses the SQL*Connect products or the new
    Transparent and Procedural Gateway products.
    Does Oracle7 Server use XA to coordinate Oracle7-only distributed
    transactions?
    No, it uses an internal mechanism.
    Can database links be used with XA?
    If an Oracle7 database is running under XA, it can access other Oracle7
    databases through database links, with some restrictions. First, the
    access to the other database must use SQL*Net V2 and be running MTS.
    Second, it must currently be to another Oracle7 database. Assuming those
    restrictions, the Oracle 7 database can do distributed update to another
    Oracle 7 database by using a database link, whether it is started by an
    Oracle application or a TP Monitor application. The TPM will see Oracle
    as only a single RM, but Oracle7 will propagate all the transaction
    commands to the other database, including the two-phase commit. If
    the transaction is started by a TP Monitor application and is using XA,
    it can also update non-Oracle resources managed by the TPM. If it
    is started from an Oracle application, it can only include resources
    managed by Oracle.
    Here's a sample configuration:
    | TPM | | TPM |
    | client | | client |
    | |
    | |
    | TPM |
    | |
    | |
    | Oracle | Forms, Forms, | Oracle | | non-XA | | XA |
    | client | Plus, Plus, | client | | TPM | | TPM |
    --------- Pro, Pro, --------- | server | | server |
    | Financials, Financials, | |(note 1)| ----------
    | etc. etc. | ---------- |
    | | | |
    | SQL | SQL | SQL | XA
    | commit | commit | commit | commit
    | | | |
    | Oracle | | Oracle | | Oracle | | Oracle |
    | server | | server | | server | | server |
    | | | |
    | | | |
    | | | |
    | Database 1 | | Database 2 |
    | | | |
    | A | A
    | | dblink to database 1 | |
    | ------------------------------------ |
    | |
    dblink to database 2
    Note 1: Oracle will work having both XA and non-XA servers but some TPMs
    may have restrictions on this.
    Are multiple direct connections possible from a Pro* program?
    Using XA, you can not only specify multiple direct connections to Oracle7
    databases, you can also update them both in the SAME transaction. The
    way to do this is to use a precompiler feature called a named database.
    When you use a named database, you qualify the SQL statement with the
    database name. For example, you write EXEC SQL AT dbname UPDATE emp ....
    We have a complementary feature in the xa open string to let the user
    associate the name with a particular RM instance, called the DB clause.
    You will also want to use the SqlNet clause in the open string so you
    can give the two different SIDs. This clause does not require the use of
    the SQL*Net product, it is just a naming convention. For more information,
    see Oracle7 Server for UNIX Administrator's Reference Guide.
    Some TP Monitors may not support having multiple Resource Mangers in the
    same server; check with the TPM vendor.
    Is there any collateral available for XA or TP Monitors?
    Oracle At Work 52684.0692
    Oracle7 Server for UNIX Administrator's #A10324-1
    Reference Guide
    Guide to Oracle's Products and Services #A10560
    Oracle7 Server and CICS/6000               #A14200
    Where can I get more information on the DTP model?
    X/Open's address is
    X/Open company Ltd (Publications)
    P O Box 109
    Penn
    High Wycombe
    Bucks HP10 8NP
    Tel: +44 (0)494 813844
    Fax: +44 (0)494 814989
    Request
    G307 Distributed Transaction Processing: Reference Model Version 2
    X/Open Guide G307 ISBN 1-859120-19-9 28cm.44p.pbk.220g.11/93
    Page(4/4)
    This file contains commonly asked questions about Oracle Server and UNIX
    Transaction Processing Monitors (TPMs). The topics covered in this article are
         o Performance with Oracle Server and TP monitors
         o Performance using Oracle's XA Library
    The questions answered in part 4 provide additional detail to the information
    provided in part 1.
    Performance with Oracle Server and TP Monitors
    ==============================================
    I have heard that Transaction Processing Monitors (TPMs) will increase
    Oracle Server performance. Is this true?
    Several hardware and TPM vendors have made the claim that TPMs
    will increase RDBMS performance. This claim is based on TPC-A
    benchmarks. The key point to understand about TPC-A is that it
    requires, for every transaction-per-second, ten times that many
    users to be connected. For example, to get 600 TPS, you need 6000
    users. The next question will answer in more detail how the the
    three-tier architecture addresses this requirement, but first let's
    look more generally at what TP Monitors can and can't do to improve
    performance.
    TP Monitors can provide better performance:
    (1) When there are more than several hundred users connected.
         This is because of the TP Monitor's role in the three-tier
         architecture, described in the next question. In this
         architecture, terminal handling is offloaded to one or more
         separate machines, freeing up those cycles to do database work.
         Note that this does NOT mean that Oracle itself runs faster,
         just that we've given it more CPU cycles to use.
    (2) When, because of the high potential concurrency of requests,
         significant resource contention exists. Use of a TP Monitor can
         limit the degree of concurrency and thus reduce contention.
    TP Monitors can not provide better performance:
    (1) For existing applications. The applications must be designed
         to fit the TP Monitor architecture.
    (2) For applications which are highly interactive in their use of
         the database. These applications put many messages
         through the transport system, and the TP Monitor is not as
         efficient as SQL*Net for point-to-point communication.
    (3) For CPU intensive single-query decision support. When executing
         a single large command, Oracle query facilities work efficiently,
         especially with the use of Oracle Parallel Query, available in 7.1.
    How does the three-tier solution help TPC-A, or other situations with
    thousands of on-line users?
    The TPC-A test calls for a large number of users to produce a given
    result. In the high-end results we produced in June, 1992, for example,
    6150 terminals were simulated to produce 618 TPC-A transactions.
    Thus, terminal concentration accounts for a large portion of the total
    processing time used.
    First, let's look at how the Multi Threaded Server would work for
    this benchmark. In this case, there are many client processes,
    but only a few server processes, which handle client requests on a
    first-come first serve basis. When they are done with a request,
    they take another client's request.
    ORACLE7 CLIENT/SERVER ARCHITECTURE WITH MULTI THREADED SERVER
    | Client | | Server |
    | __________ |______________|_____ _____________ _____________ |
    | | Client | | SQL*Net | |_|Dispatcher | | | |
    | | Process| | | ____| Process |___| | |
    | |________| | | | __|___________| | | |
    |____________| | | | | | | | |
    | | | | | | Oracle7 | |
    ______________ | | | __|__|____ | Server | |
    | Client | | | | __|_|_____ | | | |
    | __________ | | | | | Shared | |____| | |
    | | Client | | SQL*Net | | | | Server |_|____| | |
    | | Process|_|______________|__| | | Process|_| | | |
    | |________| | | | |________| |___________| |
    |____________| | | |
    | | |
    ______________ | | |
    | Client | | | |
    | __________ | | | |
    | | Client | | SQL*Net | | |
    | | Process|_|______________|____| |
    | |________| | | |
    |____________| | |
    |_______________________________________|
    Client processes = N Dispatcher processes >= 1
    Shared server processes >= 1
    If there are 500 clients in this environment, there will be one or more
    dispatcher processes, dynamically tunable, and one or more shared
    server processes, dynamically tunable, on the server. The reduction
    in the total number of processes handled by the server system
    results in more processing time available for RDBMS activity. Thus
    higher RDBMS transaction throughput can be obtained on the
    server system.
    But the problem for the TPC-A, and for certain large customer
    configurations, is not the only ability of the Oracle Server to
    process transactions, but also the ability of the operating
    system to handle huge numbers of incoming connections.
    There is one incoming connection for each client. Most UNIX
    operating systems have a limit on how many such connections they can
    handle. Even if a particular operating system allows a large number of
    connections, each takes some amount of overhead to manage.
    In order to service all 6150 terminals, we selected a 3-tier hardware
    environment where the middle tier, using a TPM, acted as a terminal
    concentrator. The high-end TPC-A architecture looked like the following.
    The Application Servers, which contain the Pro*C statements used to
    perform the transaction also run on the terminal concentrator machine
    in order to offload as much work from the database serve as possible.
    They send the compiled SQL over SQL*Net to the Oracle7 Server processes.
    ORACLE7 TPS-A CLIENT/SERVER ARCHITECTURE
    | Client | | Terminal | | Server |
    | ________ | | Concentrator | | |
    | | Client | |TPM | | | |
    | | Process|_|_____|__ _____ | | |
    | |________| |Comm | | | | | | |
    |____________| | | | | | | |
    | |__| | | | |
    ____________ | | TPM | | | |
    | Client | | ___| | _______ | | ________ _______ |
    | ________ | | | | |_| |__|_______|__| Oracle | | | |
    | | Client | |TPM | | | | |Appl. | |SQL*Net| | Server |__| | |
    | | Process|_|_____|_| |_____| |Server | | | | Process| | | |
    | |________| |Comm | |_______| | | |________| | | |
    |____________| | | | | | |
    |_______________________| | | | |
    | | | |
    ____________ _______________________ | |Oracle7| |
    | Client | | Terminal | | |Server | |
    | ________ | | Concentrator | | | | |
    | | Client | |TPM | | | | | |
    | | Process|_|_____|__ _____ | | __________ | | |
    | |________| |Comm | | | | _______ |SQL*Net| | Oracle | | | |
    |____________| | | | |_| |__|_______|__| Server |__| | |
    | |__| | |Appl. | | | | Process| | | |
    ____________ | | TPM | |Server | | | |________| |_______| |
    | Client | | ___| | |_______| | | |
    | ________ | | | | | | | |
    | | Client | |TPM | | | | | | |
    | | Process|_|_____|_| |_____| | | |
    | |________| |Comm | | | |
    |____________| | | | |
    |_______________________| |________________________|
    Clients = 6150 Terminal concentrators = 17
    TP Monitor instances = 17
    Application server processes Oracle Server processes
    = 17*8 = 17*8
    The TPM is the software component of the terminal concentrator. In this role
    it offloads terminal handling from the the machine running Oracle Server.
    Since more than one terminal concentrator can be configured, whereas the
    database in this case had to run on a single machine, concentrator machines
    can be added until the performance of the back-end machine was optimized.
    This three-tier solution resulted in the outstanding transaction throughput
    announced with Oracle7 Server. Even with Oracle Parallel Server, it may pay
    to offload the terminal handling so that the cluster can be exclusively used
    for database operations.
    Can you summarize the performance discussion for me?
    Depending on the number of users required, different architectures may be
    used in a client/server environment to maximize performance:
    1) For a small number of users, the traditional Oracle two-task
    architecture can be used. In this case, there is a one-to-one
    correspondence between client processes and server processes. It's
    simple, straightforward, and efficient.
    2) For a large number of users, Multi Threaded Server might be a better
    approach. Although some tuning may be required, Multi Threaded Server
    can handle a relatively large number of users for each machine size
    compared to the traditional Oracle approach. Using this approach,
    customers will be able to handle many hundreds of users on many
    platforms. Furthermore, current Oracle applications can move to this
    environment without change.
    3) For a very large number of users, where transactions are simple and
    terminal input concentration is the overriding performance issue, a
    3-tier architecture incorporating a TPM may be useful. In this case,
    terminal concentration is handled by the TPM in the middle tier. As
         you might expect, it is a more complex environment requiring more
         system management. For existing Oracle customers, significant Oracle
    application modifications will be required.
    Oracle provides all of these choices.
    Performance using Oracle's XA Library
    =====================================
    Are there any performance implications to using the XA library (in other
    words, to using TPM-managed transactions)?
    (1) The XA library imposes some performance penalty. You should use
    TPM-managed transactions only if you actually need them. Even if you
    are getting the one-phase commit optimization, the code path is
    longer because we need to map back and forth between external
    formats and internal ones. Also, prior to 7.1, XA requires you
    to release all cursors at the end of a transaction, which results
    in extra parsing. Even with shared cursors, there is time spent
    looking up the one you need and re-validating it. This has been
    improved for 7.1.
    (2) If you need to use two-phase commit, this will incur additional cost
    since extra I/Os are required. If you do need 2PC, you need to account
    for that when sizing the application.
    (3) Although some TPMs allow parallel execution of services (such as Tuxedo's
    "tpacall"), this will not normally enhance performance unless different
    resource managers are being used. In fact, Oracle Server must serialize
    accesses to the same transaction by the same Oracle instance, and the
    block/resume code will in fact degrade performance in that case compared
    to running the services sequentially.

    hello,
    the role is the same on all plattforms. the reports server takes requests for running reports, spawns an engine that executes the request. in addition to that, the server also provides scheduling services and security features for the reports environment.
    regards,
    the oracle reports team

  • How to Start Oracle Report in Unix?

    hi
    Does anyone know how to start oracle report in unix? I was
    told to try this (r60desm) but that did not work. We are on 11i
    and 6i. Please help
    alpha

    I don't have Forms/Reports 6i for UNIX. Have you tried typing "r60" and typing tab twice?

  • ORACLE SERVER AND UNIX TP MONITOR-1

    제품 : ORACLE SERVER
    작성날짜 : 2002-05-17
    ====================================================================
    Subject: Oracle Server and UNIX Transaction Processing Monitors - 1
    =====================================================================
    PURPOSE
    This file contains commonly asked questions about Oracle Server and UNIX
    Transaction Processing Monitors (TPMs). The topics covered in this article are
         o What is a Transaction Processing Monitor (TPM)?
         o What is the X/Open Distributed Transaction Processing Model?
         o How does the Oracle Server works with TPMs?
         o How should I position TPMs with my customer?
         o What Oracle products must a customer purchase?
         o Where can my customer purchase a TPM?
         o Availability and packaging
    Explanation & Example
    What is a Transaction Processing Monitor?
    =========================================
    Under UNIX, a Transaction Processing Monitor (TPM) is a tool that coordinates
    the flow of transaction requests between front-end client processes that issue
    requests and back-end servers that process them. A TPM is used as
    the "glue" to coordinate transactions that require the services of several
    different types of back-end processes, such as application servers and
    resource managers, possibly distributed over a network.
    In a typical TPM environment, front-end client processes perform screen
    handling and ask for services from back-end server processes via calls to the
    TPM. The TPM then routes the requests to the appropriate back-end server
    process or server processes, wherever they are located on the network. Through
    configuration information, the TPM knows what services are available and where
    they are located. Generally, the back-end server processes are specialized so
    that each one handles one type of requested service. The TPM provides
    location transparency as well and can send messages through the network
    utilizing lower-level transport services such as TCP/IP or OSF DCE.
    The back-end servers process the requests as necessary and
    return the results back to the TP monitor. The TP monitor then routes
    these results back to the original front-end client process.
    A TPM is instrumental in the implementation of truly distributed processing.
    Front-end clients and back-end processes have no knowledge of each
    other. They operate as separate entities, and it is this concept that provides
    flexibility in application development. Front-end and back-end processes are
    developed in the UNIX client-server style, with each side optimized for its
    particular task. Server functionality can be deployed in stages, which makes
    it easy to add functionality as needed later in the product cycle. It also
    makes it easy to distribute both the front-end and back-end processes
    throughout the network on the most appropriate hardware for the job. In
    addition, multiple back-end server processes of the same type might be
    activated to handle increasing numbers of users.
    What is the X/Open Distributed Transaction Processing Model?
    ============================================================
    The X/Open Transaction Processing working group has been working
    for several years to establish a standard architecture to implement
    distributed transaction processing on open systems. In late 1991,
    X/Open published the initial Distributed Transaction Processing (DTP)
    model specification and defined the first of several interfaces that
    exist between the components of the model. Subsequently, other publications
    and a revised model specification have been published.
    An important function of the TPM in the X/Open DTP model is the
    synchronization of any commits and rollbacks that are required to complete
    a distributed transaction request. The Transaction Manager (TM) portion
    of the TPM is the entity responsible for ordering when distributed commits
    and rollbacks will take place. Thus, if a distributed application program
    is written to take advantage of the TM portion of the TPM, then it,
    and not the DBMS, becomes responsible for enabling the two-phase commit
    process. Article 2 has more detail on this model.
    How does the Oracle Server work with TPMs?
    ==========================================
    When a TPM is used without invoking an X/Open TM component to manage the
    transactions, Oracle Server needs no special functionality. The transaction
    will be managed by Oracle itself. However, when the TPM X/Open TM component
    is used to manage the transaction, the Oracle Server, that is the Oracle DBMS,
    acts as a Resource Manager--a type of back-end process. In the case of
    TPM-managed transactions, the TM needs a way to tell the RMs about the stages
    of the transaction. This is done by a standard, X/Open defined interface
    called XA. Article 2 of of this document gives more information about both
    the X/Open model and Oracle7's use of XA.
    Because the XA interface provides a standard interface between the TM and the
    resource manager, it follows that the TM can communicate with any XA-compliant
    resource manager (e.g., RDBMS), and, conversely, that a resource manager can
    communicate with any XA-compliant TM. Thus, the Oracle Server, beginning with
    Oracle7, works with any XA-compliant TM.
    How should I position TPMs with my customer?
    ============================================
    There's been a great deal of confusion about the need for TPM technology. Some
    software suppliers, most notably IBM, will assert that a TPM like CICS is a
    necessary requirement for high volume OLTP. Other vendors will assert that
    there is seldom a need for such technology. And yet others promote TPMs as
    providers of higher transaction throughput.
    From Oracle's standpoint, customers might choose TPM technology under any of
    the following conditions:
    1. For heterogeneous database access, especially for 2PC capability
         This means that a TPM can be used to coordinate 2PC between Oracle
         DBMS and any other XA-compliant database, such as Informix. This
         does NOT provide SQL heterogeneity - SQL calls to Oracle DBMS may be
         different than SQL calls to Informix. The TPM handles the routing,
         communication, and two-phase commit portion of the transaction, but
         does not translate one type of SQL call into another.
    2. For transaction monitoring and workload control
         The leading TPMs supply tools to actively manage the flow of
         transactions between clients and servers and to load balance the work
         load across all available processors on a network, not just on a
         single multi-processor system. Some TPMs also have the ability to
         dynamically bring up additional back-end services during peak work
         hours.
    3. For more flexible application development and installation
         One of the key features of the DTP model is application modularity.
         Modularity, that is, the decomposition of a large program into small,
         easily defined, coded and maintained "mini-programs" makes it easy to
         add new functionality as needed. Modularity also makes it much easier
         to distribute the front-end and back-end processes and the resource
         managers across hardware throughout a network.
    4. For isolating the client from details of the data model
    By using the service oriented programming model, the client program
         is unaware of the data model. The service can be recoded to use a
         different one with no change to the client. To get this advantage,
         the application developer must explicitly code the server and client
         to fit the service model.
    5. For connection of thousands of users
         TP Monitors, because of their three-tier architecture, can be used
         to connect users to an intermediate machine or machines, removing
         the overhead of handling terminal connections from the machine
         actually running the database. See Article 4 for more information.
    There are also several cases where TPM technology is not the right answer.
    These include:
    1. If the customer is simply looking for a performance improvement
         The customer may have heard a theory that "higher performance
         is possible for large scale applications only if they use a
         TP monitor". First, no performance gain can be achieved for
         existing applications; in fact, they won't even run under a TP
         Monitor without recoding. Second, performance improvements have
         only been documented for large numbers of users, and "large"
         means many hundreds or thousands. Without a TP Monitor,
         Oracle Server can handle several hundred users with its normal
         two-task architecture and several times that using the Multi
         Threaded Server. For more on performance, see Article 4.
    2. If the customer has made large investment in his existing Oracle
    applications
         TP monitor applications must be designed from the ground up to take
         advantage of TP monitor technology. Current Oracle customers will find
         it difficult to "retrofit" a TP monitor to their existing applications.
         The Multi Threaded Server, on the other hand, allows the use of
         existing Oracle applications without change.
    3. If the customer is committed to the Oracle tool set
         Currently, none of Oracle's front-end tools (Oracle Forms, etc.) is
         designed to work with TP monitors. It is possible to invoke a
         TP Monitor by using user exits. However, the fact that the TP
         Monitor model hides the data model from the client means that only
         the screen display parts of Forms can be used, not the automatic
         mapping from screen blocks to tables.
    4. If the customer does not have a staff of experienced software engineers
         This is still very young technology for UNIX. There is not a lot of
    knowledge in the industry on how to build TP monitor applications or
    what techniques are most useful and which are not. Furthermore,
         integrating products from different vendors, even with the support
         of standard interfaces, is more complex than deploying an integrated
         all-Oracle solution. Because TP monitor technology is fairly
         complex, we recommend that you let the TP monitor supplier promote
         the virtues of their technology and differentiate themselves from
         their competitors.
    What Oracle products must a customer purchase?
    ==============================================
    If your customer is only interested in building Oracle-managed TP Monitor
    transactions, the only Oracle products required are the Oracle Server
    and the appropriate Oracle precompiler for whatever language the
    application is being written in--most likely C or Cobol. If TPM-managed
    transactions are required, the Oracle7 Server with the distributed option
    is also required. SQL*Net is optional because the TPM takes care of the
    network services. Article 2 describes when you would choose to have the TP
    Monitor manage the transactions.
    Where can my customer purchase a TPM?
    =====================================
    There are many vendors offering the UNIX TPM products. (Oracle does not
    relicense TPMs.) Information on the most well known products is provided
    below:
    The following support XA:
    Product & Vendor     FCS          Known OS/Platform Ports
    "TUXEDO System/T"     1986          UNIX SVR4 & SVR3: Amdahl, AT&T,
    UNIX System Laboratories          Bull, Compaq, Dell, Fujitsu, ICL,
    190 River Road                    Motorola, Olivetti, Pyramid,Sequent,
    Summit, NJ 07901               Sun, Toshiba, Unisys, NCR, Stratus
                             Other: IBM AIX, HP/UX, DEC Ultrix
    "TOP END"      1992          UNIX SVR4: NCR
    NCR Corporation
    1334 S. Patterson Blvd.
    Dayton, OH 45479
    "ENCINA"          1992          IBM AIX, HP, Sun (SunOS and Solaris)
    Transarc Corporation               Other: OS/2, DOS, HP-UX, STRATUS
    707 Grant Street (Depends on DCE)
    Pittsburgh, PA 15219
    "CICS/6000" 1993          AIX: IBM
    IBM Corporation                    (Depends on DCE)
    "CICS 9000" 1994          HP-UX
    HP
    The following do not currently support XA:
    Product & Vendor     FCS          Known OS/Platform Ports
    "VIS/TP"          unknown          unknown
    VISystems, Inc.
    11910 Greenville Avenue
    Dallas, TX 75243
    "UniKix"          1990          UNIX: ARIX, AT&T, NCR, Pyramid,
    UniKix                     Sequent, Sun, Unisys      
    "MicroFocus           1993          SCO Unix, AIX
    Transaction System"
    Micro Focus
    26 West Street
    Newbury RG13 1JT
    UK
    There are also several third parties who are reselling the products listed
    above.
    In addition, Groupe Bull, Digital, Siemens-Nixdorf, and several other hardware
    vendors are planning to redesign their proprietary TPMs to be XA-compliant and
    suitable for use on UNIX systems.
    Availability and Packaging
    ==========================
    On what platforms is the XA Library available?
    Oracle provides the XA interface with Oracle7 Server on all platforms that
    support an XA-compliant TPM. Support for XA is included as part of the
    Oracle7 Server distributed option and has no extra charge in and of itself.
    Which version of XA does Oracle Server support?
    Oracle7 Server supports the Common Application Environment (CAE) version of
    XA, based on the specification published by X/Open in late 1991. It will
    require that the TM also be at that level. This means Tuxedo /T version 4.2,
    for example.
    Oracle Server supports all required XA functions. There are some optional
    features Oracle Server does not support, such as asynchronous operation.
    None of those options affect application programming.
    Page (2/4)
    This file contains commonly asked questions about Oracle Server and UNIX
    Transaction Processing Monitors (TPMs). The topics covered in this article are
         o Oracle Server Working with UNIX TPMs
         o TPM Application Architecture
    The questions answered in part 2 provide additional detail to the information
    provided in part 1.
    Oracle Server Working with UNIX TP Monitors
    ===========================================
    Do I need XA to use Oracle Server with TPMs? If I don't use it, what are
    the consequences?
    There are a number of real applications running today with Oracle Server and
    TPMs but not using XA. To use a TPM with Oracle without using XA, the user
    would write an "application server" program which could handle one or more
    "services". For example, a server program might handle a service called
    "debit_credit". The key requirement is that the entire transaction,
    including the "commit work", must be executed within a single service. This
    is the restriction which XA will remove, as we'll see later. Each
    server process can serially handle requests on behalf of different clients.
    Because a server process can handle many client processes, this can
    reduce the total number of active processes on the server system,
    thereby reducing resource requirements and possibly increasing overall
    throughput.
    When Oracle is used with a TPM in this mode, we call it an Oracle-managed
    transaction since the transaction commit or rollback is done with a SQL
    statement.
    What is XA? How does XA help Oracle7 work with UNIX TPMs?
    XA is an industry standard interface between a Transaction Manager and a
    Resource Manager. A Resource Manager (RM) is an agent which
    controls a shared, recoverable resource; such a resource can be
    returned to a consistent state after a failure. For example, Oracle7 Server
    is an RM and uses its redo log and undo segments to be able to do this.
    A Transaction Manager (TM) manages a transaction including the
    commitment protocol and, when necessary, the recovery after a failure.
    Normally, Oracle Server acts as its own TM and manages its own commitment
    and recovery. However, using a standards-based TM allows Oracle7 to
    cooperate with other heterogeneous RMs in a single transaction.
    The commonly used TPMs include a TM component for this purpose. In order to
    use the TM capability of the TPM rather than Oracle7's own transaction
    management, the application uses a transaction demarcation API (called TX)
    provided by the TPM rather than the SQL transaction control statements (e.g.
    "commit work"). For each TX call, the TM then instructs all RMs, by the
    appropriate XA commands, to follow the two-phase commit protocol. We
    call this a TPM-managed transaction.
    The following picture shows these interfaces within a monolithic application
    program model. This is the model most commonly described in the
    DTP literature. We'll see later what the picture looks like when we add
    Oracle7 and when we switch to a modularized client-server application
    program model.
              | |
              | |
              | Application Program (AP) |
              | |
              | |
                   | | |                    |
    Resource Manager API | | | |
    (e.g. SQL) -----|--|------------- | TX API
              | | v |          |
              --------|-------------     |          |
              | v | | v
         ---------------------- | | --------------------
         | | | | | |
         | Resource | | |<----->| Transaction |
         | Managers | |--- | Manager |
         | (RMs) | |<-------->| (TM) |
         | |--- | |
         | |<----------->| |
         ---------------------- XA --------------------
                        Interface
    The XA interface is an interface between two system components, not
    an application program interface; the application program does
    not write XA calls nor need to know the details of this interface.
    The TM cannot do transaction coordination without the assistance of
    the RM; the XA interface is used to get that assistance.
    How does the DTP Model support client-server?
    The above picture was actually simplified to make it easier to explain
    the role of XA. In a true distributed transaction architecture, there
    are multiple applications, each with an Application Program, a Resource
    Manager, and a Transaction Manager. The applications communicate by
    using a Communication Resource Manager. The CRM is generally provided
    as a component of the TPM. It includes the transaction information when
    it sends messages between applications, so that both applications can
    act of behalf of the same transaction. The following picture
    illustrates this:
    Client Application
    | AP |
    ||| | |
    SQL ||| | TX | CRM
    ||V V | API
    -||-- ----- |
    | |V | | | V
    --|-- |<---| | -----
    | V || | | | |
    ----- |<----| TM |<-->| CRM |
    | || | |XA+ | |
    | RMs |<-----| | -----
    | | XA | | A
    ----- ----- | Server Application
    | -----------------------------
    | | AP |
    | -----------------------------
    | ||| | |
    | SQL ||| | TX | CRM
    | ||V V | API
    | -||-- ----- |
    | | |V | | | V
    | --|-- |<---| | -----
    | | V || | | | |
    | ----- |<----| TM |<-->| CRM |
    | | || | |XA+ | |
    | | RMs |<-----| | -----
    | | | XA | | A
    | ----- ----- |
    | |
    | |
    -------- |
    / |
    / |
    / |
    Most TP Monitor products include both a TM and a CRM, and also provide
    additional functions such as task scheduling and workload monitoring.
    What is XA+? What does Oracle need to do to comply with it?
    XA+ is an interface that lets the X/Open model actually be distributed
    because it allows a communication resource manager to tell a TM on the
    server that a message from a client just came in for a particular
    transaction. Oracle is not currently planning to provide an X/Open
    communication resource manager, so we don't have any plans right now
    to do XA+. Version 2 of the DTP model paper from X/Open describes it.
    The status of the current XA+ specification is "snapshot".
    When would I choose an Oracle-managed transaction vs a TPM-managed
    transaction?
    Oracle Server is very efficient at managing its own transactions. If
    the TPM manages the transaction, in general some additional overhead
    will be incurred.
    The two main reasons a customer might prefer to use a TPM-managed
    transaction are as follows:
    (1) He may need to update RMs from different vendors. Experience so far
    has been that the most common case is wanting to update both Oracle and
    a TP Monitor managed resource such as a transactional queuing service
    in the same transaction (see Article 3).
    (2) He may want to use the model of having several different services in
    a transaction, even to the same database. For example, the
    "debit_credit" service could be split into a "debit" service and a
    "credit" service. This is a very attractive model, but this type of
    modularity does exact a performance penalty (see Article 4).
    Can I get a version of XA to run on Oracle Server version 6?
    No, the XA functionality uses two underlying mechanisms in the Oracle
    Server which are not available in version 6: two-phase commit and
    session switching. The upi calls for these functions do not not exist
    in version 6.
    When would I use XA vs Oracle7 to coordinate all-Oracle distributed
    transactions?
    Generally speaking, Oracle Server should be used to coordinate all-Oracle
    distributed transactions. The main reason for using XA to coordinate
    transactions would be that you want to use the TP Monitor service-oriented
    architecture. That is, you would like to construct an application built of
    services and service requests in order to benefit from the modularity and
    workload control such an environment provides.
    TP Monitor Application Architecture
    ===================================
    What might a TP Monitor application look like?
    Most TPM applications will consist of two more more programs, where
    there are front-end client programs which request services and back-end
    server programs which provide services. In this case, the TPM supplies an
    additional capability which is transactional communication. The client
    describes the boundaries of the transaction, through the use of the TX API,
    and the TPM relays that transaction information to each requested service.
    The overall application structure generally looks like the following in the
    client-server model. The "TP Monitor Services" box is not necessarily a
    process. It could be one or more processes, or just libraries coordinating
    through shared memory. Each client process and server process could be on
    a different machine. Normally, the application server processes would be
    connected to their Oracle Server processes using the IPC driver; the TPM
    would be used to deliver messages between application client processes on
    one machine and application server processes on another. However, the
    application server processes could also be connected with the standard
    Oracle SQL*Net to shadow processes on different machines. This might be
    useful if one of the databases was on a machine which did not support TPMs.
    |Application| |Application| |Application|
    | Client 1 | | Client 2 | | Client 3 |
    | | | | | |
    \ TPM API | TPM API / TPM API
    | |
    | TP Monitor Services |
    | |
         | --------------------- |
    | | Transaction Manager | |
    ---------------|---------------|---------------------
    TPM API | | XA | XA | TPM API
    | | inter- | inter- |
              | | face | face |
              | | | |
    ----------- | | -----------
    |Application| | | |Application|
    | Server 1 |--- ---| Server 2 |
    | (Pro*C) | | | | (Pro*C) |
    | SQL | SQL
    | | | |
    | Resource ----------- ----------- |
    | Manager | | | | |
    | | Oracle7 | | Oracle7 | |
    | | Server | | Server | |
    | | Process | | Process | |
    | | | | | |
    | ----------- ----------- |
    | | | |
    | ----------------------------------------------------- |
    | | | |
    | | SGA | |
    | | | |
    | ----------------------------------------------------- |
    | |
    Application client programs might be written in C and be linked with
    TPM libraries. Alternatively, they could use a screen painter product.
    Application server programs would be written in Pro*C or Pro*COBOL and
    be linked with TPM libraries, the normal Oracle7 user-side libraries
    and libxa.a. The Oracle7 Server process is the regular Oracle7 executable.
    More complicated application architectures can also be constructed. Most of
    the TPMs allow a server to become a client of another service, so you can
    involve additional servers.
    Could I use Oracle7's Multi Threaded Server as the SQL*Net connection in the
    previous picture?
    Yes, but that will not be needed in many cases. For example, both
    application server processes in the previous picture could talk to a
    single Oracle7 Server process through the Multi Threaded Server in the
    previous picture. However, since the TPM architecture typically reduces
    the number of server processes, the reduction in processes using Multi
    Threaded Server may be less significant than in an architecture without
    TPMs. If the application will use database links, however, then MTS will
    be required.
    How do I write an Oracle TP Monitor application?
    The actual API used to talk to the TPM varies between vendors, so you need
    to get the documentation from the vendor. However, all have a way to
    indicate where a transaction begins and ends and a way to send a request
    and receive a response from a client to a server. Some use an RPC model,
    some use a pseudo-RPC model, and some use a send/receive model. The TX API
    described earlier is a subset of the TPM API as defined by each of
    the TPM providers.
    The client program and server program might look something like the
    following examples. We h (such as Tuxedo's
    "tpacall
    Reference Ducumment
    ---------------------

    hello,
    the role is the same on all plattforms. the reports server takes requests for running reports, spawns an engine that executes the request. in addition to that, the server also provides scheduling services and security features for the reports environment.
    regards,
    the oracle reports team

  • How to connect oracle database in UNIX OS

    Hi All
    can any one help me on how to connect to oracle database in UNIX system(PUTTY)..
    Generally what i am doing is
    1) login with my user name
    2) trying to connect oracle using the command sqlplus -s username/password
    showing error SQLPLUS: not found
    Do i need to go any path where oracle is install? iF yes, how to find out that? or any other step to connect? Please help me by giving the sequence of steps...
    Regards
    Prem Raj Dasari

    What is your database version?
    can any one help me on how to connect to oracle database in UNIX system(PUTTY)..
    Generally what i am doing is
    1) login with my user name
    2) trying to connect oracle using the command sqlplus -s username/password
    showing error SQLPLUS: not found
    Do i need to go any path where oracle is install? iF yes, how to find out that? or any other step to connect? Please help me by giving the sequence of steps...You need to source the database env file before running sqlplus.
    R12 -- Maintaining Oracle E-Business Suite Documentation Set
    http://docs.oracle.com/cd/B53825_08/current/html/docset.html
    11i -- Maintaining Oracle Applications Documentation Set
    http://docs.oracle.com/cd/B25516_18/current/html/docset.html
    Thanks,
    Hussein

  • Running Oracle Reports in unix, output in pdf file

    Hi all,
    Anybody currently running Oracle Reports in unix platform and the output is generated in pdf format & display in browser?
    Can you please advise on what are all the environment variables that I have to set in order to get the report runs?
    Besides, what are the specific printer setting that I have to set? as well as priviledge on directory if necessary.
    My reports are created in PC with RDF format. When run in unix, can the RDF still be used or it has been to recompile? If recompile, how is this done?
    I always get the following error but do not what is the cause:
    REP-0110: Unable to open file 'myreport.rdf'. REP-1070: Error while opening or saving a document. REP-0110: Unable to open file 'myreport.rdf'.
    Please advise.
    Hope to receive your reply asap.
    Great thanks in advance.

    What command did you type in to run your report in Unix? Did you give the full path of your rdf file. I guess that the system may not be find your rdf file correctly.
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by guest2000:
    Hi all,
    Anybody currently running Oracle Reports in unix platform and the output is generated in pdf format & display in browser?
    Can you please advise on what are all the environment variables that I have to set in order to get the report runs?
    Besides, what are the specific printer setting that I have to set? as well as priviledge on directory if necessary.
    My reports are created in PC with RDF format. When run in unix, can the RDF still be used or it has been to recompile? If recompile, how is this done?
    I always get the following error but do not what is the cause:
    REP-0110: Unable to open file 'myreport.rdf'. REP-1070: Error while opening or saving a document. REP-0110: Unable to open file 'myreport.rdf'.
    Please advise.
    Hope to receive your reply asap.
    Great thanks in advance.<HR></BLOCKQUOTE>
    null

  • Guidelines regarding directory structure for multiple Oracle homes on Unix!

    Hi All,
    Are there any guidelines published regarding directory structures that should be defined while using multiple Oracle homes on Unix/Linux box?
    I am looking for guidelines regarding admin and oradata folders so that we dont accidentally mess up with the DB contents with a wrong Oracle home.
    Its a development server with 8i and 10g. 11g might also get loaded on the same server in future.
    Thanks in advance...
    Regards

    Thanks Maran.
    I have already checked many installation guides before posting here. All of them mention about creating folders like /admin or /oradata on various mount points but none of the naming conventions really indicate whether it is a 8i database or a 10g database.
    This is required when you are having multiple Oracle installations under /opt and databases are running from different mount points.
    Regards,

  • Oracle Streams:  Oracle 10g in Unix to Oracle 10g in Windows 2003

    Hello,
    At our company, we wish to migrate one of our Oracle 10g databases from Windows 2003 to Unix environment. With this new Oracle database in Unix, we would like to connect it via Linked Streams to another Oracle 10g database in a Windows 2003 environment.
    My question is: Is this possible? If so, what middleware/other components would we need to set this up?
    Thanks!
    Edited by: user3031139 on Sep 16, 2008 7:18 AM

    You can use any of the samples in the official Oracle docs:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14229/pt_demos.htm#sthref1277
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14228/ptrep_demos.htm#BEIDDCBI
    There is simply nothing special that has to be done for the different OS.

  • How to run oracle forms in Unix

    How to run Oracle forms in unix ?'

    Oracle Forms only runs on an Oracle application Server.
    Regards
    Grant Ronald
    Oracle Product Management

  • Run Report outside Oracle Application on Unix box

    i want custom repot output outside Oracle Application on Unix box. How could i get output, which command i have to use. i can run on PC.

    Hi,
    Do you want to print the report NOT from the application? If so, you can use lp or print commands to do this (Output files can be found under $APPLCSF/$APPLOUT directory).
    Note: 106186.1 - How to Test an Initialization String Outside of Oracle Applications
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=106186.1
    You can also print the report from the OS using CONCSUB.
    Note: 167224.1 - How to Run a Report from the Operating System Using CONCSUB
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=167224.1
    Regards,
    Hussein

Maybe you are looking for

  • MacBook Pro with 30 inch Cinmea HD - Mirroring

    I just discovered that when I have my Cinema HD display connected to my MB Pro and I have the lid of the MB Pro closed then I don't have to use two displays - the MB Pro's and the Cinema HD display - and that the menu bars etc all appear on the Cinem

  • Podcasts in the Main Library

    I am looking for a way for Podcasts to show up when I shuffle through my whole library.

  • Use UpdateXml

    Hi, I have a table which contains XML in a clob. The xml looks something like this: <form>      <formfield>           <fieldname>FieldA</fieldname>           <fieldvalue>aaaaa</fieldvalue>      </formfield>      <formfield>           <fieldname>Field

  • Adobe Reader doesn't open on Mac

    Hi, I cannot open PDF files on my mac.  As per other forums, I have tired deleteing and un-installing all adobe reader, then tried re-downlading it.  I still can't get the PDF's to open.  I have read through the 'terms' and agree, but it still doesn'

  • Publication with Date

    Hi, We have a small requirement. We are using Publication feature of BO to publish reports to user inboxes.  These publications are in daily base. If we are running a publication on today (1-7-2009)  it should display the report name as report as on