RDBMS version

The minimum requirement stated for headstart 6.5.3.2 for designer 9i is rdbms 9.2.0.1. Why is this the minimum requirement? Designer 9i was certified against 8.1.7.4. Only because of desupport of 8i the certification was halted.
With kind regards,
Robert Rozijn

장애 상황으로 open이 안되는 건지 아니면 startup mount를 통한 startup인지 구분이 필요하겠지만
만약 장애 상황이 아니라면
alter database open;
명령어로 mount 단계에서 open 단계로 넘어갈 수 있습니다.
만약 장애 상황에 따른 open 불가 상황이라면 장애를 복구하는 방향으로 접근해야 합니다.

Similar Messages

Optimizer bug in RDBMS versions 9.2.0.7.0 and 9.2.0.8.0

This listing below demonstrates a bug in the Oracle optimizer that causes incorrect results to be returned after a table is analyzed. Rule based optimizer gives correct results.
Under cost-based optimization the predicate includes a condition from a check constraint on a nullable field. When the value of this field is NULL the record is excluded from the results even though that record does not violate the check constraint.
I have verified that this bug exists on both RDBMS versions 9.2.0.7.0 and 9.2.0.8.0.
ORA92080>
ORA92080>DROP TABLE test1;
Table dropped.
ORA92080>DROP TABLE test2;
Table dropped.
ORA92080>
ORA92080>CREATE TABLE test1
2 ( id     NUMBER NOT NULL
3 , date1     DATE NOT NULL
4 , date2     DATE
5 );
Table created.
ORA92080>
ORA92080>ALTER TABLE test1
2 ADD ( CONSTRAINT test1_chk_date1
3      CHECK ( date1 > TO_DATE( '01-JAN-1960', 'DD-MON-YYYY' ) )
4      );
Table altered.
ORA92080>
ORA92080>ALTER TABLE test1
2 ADD ( CONSTRAINT test1_chk_date2
3      CHECK ( date2 >= date1 )
4      );
Table altered.
ORA92080>
ORA92080>/* date2 is NULL */
ORA92080>INSERT INTO test1 VALUES ( 1, TO_DATE('16-JUN-2005 11:30:01', 'DD-MON-YYYY HH24:MI:SS'), NULL );
1 row created.
ORA92080>
ORA92080>/* date2 is filled in */
ORA92080>INSERT INTO test1 VALUES ( 2
2                     , TO_DATE('16-JUN-2005 11:30:01', 'DD-MON-YYYY HH24:MI:SS')
3                     , TO_DATE('16-JUN-2005 11:40:01', 'DD-MON-YYYY HH24:MI:SS')
4                );
1 row created.
ORA92080>
ORA92080>CREATE TABLE test2 AS
2 SELECT * FROM test1
3 WHERE 1=2;
Table created.
ORA92080>
ORA92080>ALTER SESSION SET NLS_DATE_FORMAT = 'DD-MON-YYYY HH24:MI:SS';
Session altered.
ORA92080>
ORA92080>SELECT * FROM test1;
ID DATE1 DATE2
1 16-JUN-2005 11:30:01
2 16-JUN-2005 11:30:01 16-JUN-2005 11:40:01
2 rows selected.
ORA92080>SELECT * FROM test2;
no rows selected
ORA92080>
ORA92080>/*
DOC>| Since no statistics were gathered, rule-based optimizer will be used.
DOC>| The correct count of two is returned.
DOC>*/
ORA92080>SELECT COUNT(*) FROM test1 t
2 WHERE EXISTS
3      ( SELECT 'X'
4      FROM ( SELECT id, date1
5                FROM test1
6           MINUS
7           SELECT id, date1
8                FROM test2
9           ) i
10      WHERE i.id = t.id
11           AND i.date1 = t.date1
12      );
COUNT(*)
2
1 row selected.
ORA92080>
ORA92080>EXPLAIN PLAN FOR
2 SELECT COUNT(*) FROM test1 t
3 WHERE EXISTS
4      ( SELECT 'X'
5      FROM ( SELECT id, date1
6                FROM test1
7           MINUS
8           SELECT id, date1
9                FROM test2
10           ) i
11      WHERE i.id = t.id
12           AND i.date1 = t.date1
13      );
Explained.
| Id | Operation | Name | Rows | Bytes | Cost |
| 0 | SELECT STATEMENT | | | | |
| 1 | SORT AGGREGATE | | | | |
|* 2 | FILTER | | | | |
| 3 | TABLE ACCESS FULL | TEST1 | | | |
| 4 | VIEW | | | | |
| 5 | MINUS | | | | |
| 6 | SORT UNIQUE | | | | |
|* 7 | TABLE ACCESS FULL| TEST1 | | | |
| 8 | SORT UNIQUE | | | | |
|* 9 | TABLE ACCESS FULL| TEST2 | | | |
Predicate Information (identified by operation id):
2 - filter( EXISTS (SELECT 0 FROM ( (SELECT "TEST1"."ID"
"ID","TEST1"."DATE1" "DATE1" FROM "TEST1" "TEST1" WHERE
"TEST1"."DATE1"=:B1 AND "TEST1"."ID"=:B2)MINUS (SELECT "TEST2"."ID"
"ID","TEST2"."DATE1" "DATE1" FROM "TEST2" "TEST2" WHERE
"TEST2"."DATE1"=:B3 AND "TEST2"."ID"=:B4)) "I"))
7 - filter("TEST1"."DATE1"=:B1 AND "TEST1"."ID"=:B2)
9 - filter("TEST2"."DATE1"=:B1 AND "TEST2"."ID"=:B2)
Note: rule based optimization
28 rows selected.
ORA92080>
ORA92080>BEGIN
2 DBMS_STATS.GATHER_TABLE_STATS
3      ( ownname     => USER,
4      tabname     => 'TEST2',
5      estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE,
6      cascade     => TRUE
7      );
8 END;
9 /
PL/SQL procedure successfully completed.
ORA92080>
ORA92080>/*
DOC>| This is the identical query as above. With statistics gathered, the
DOC>| cost-based optimizer is used. An incorrect count of 1 is returned.
DOC>*/
ORA92080>SELECT COUNT(*) FROM test1 t
2 WHERE EXISTS
3      ( SELECT 'X'
4      FROM ( SELECT id, date1
5                FROM test1
6           MINUS
7           SELECT id, date1
8                FROM test2
9           ) i
10      WHERE i.id = t.id
11           AND i.date1 = t.date1
12      );
COUNT(*)
1
1 row selected.
ORA92080>
ORA92080>/* Using rule-based optimizer, the result is correct. */
ORA92080>SELECT /*+ RULE */ COUNT(*) FROM test1 t
2 WHERE EXISTS
3      ( SELECT 'X'
4      FROM ( SELECT id, date1
5                FROM test1
6           MINUS
7           SELECT id, date1
8                FROM test2
9           ) i
10      WHERE i.id = t.id
11           AND i.date1 = t.date1
12      );
COUNT(*)
2
1 row selected.
ORA92080>
ORA92080>EXPLAIN PLAN FOR
2 SELECT COUNT(*) FROM test1 t
3 WHERE EXISTS
4      ( SELECT 'X'
5      FROM ( SELECT id, date1
6                FROM test1
7           MINUS
8           SELECT id, date1
9                FROM test2
10           ) i
11      WHERE i.id = t.id
12           AND i.date1 = t.date1
13      );
Explained.
ORA92080>
ORA92080>SET ECHO OFF
Wrote file reset.sql
Session altered.
| Id | Operation | Name | Rows | Bytes | Cost |
| 0 | SELECT STATEMENT | | 1 | 44 | 11 |
| 1 | SORT AGGREGATE | | 1 | 44 | |
|* 2 | HASH JOIN SEMI | | 1 | 44 | 11 |
| 3 | TABLE ACCESS FULL | TEST1 | 82 | 1804 | 2 |
| 4 | VIEW | | 1 | 22 | 8 |
| 5 | MINUS | | | | |
| 6 | SORT UNIQUE | | 1 | 31 | |
|* 7 | TABLE ACCESS FULL| TEST1 | 1 | 31 | 2 |
| 8 | SORT UNIQUE | | 1 | 22 | |
|* 9 | TABLE ACCESS FULL| TEST2 | 1 | 22 | 2 |
Predicate Information (identified by operation id):
2 - access("I"."ID"="T"."ID" AND "I"."DATE1"="T"."DATE1")
7 - filter("TEST1"."DATE1">TO_DATE(' 1960-01-01 00:00:00',
'syyyy-mm-dd hh24:mi:ss') AND "TEST1"."DATE2">TO_DATE(' 1960-01-01
00:00:00', 'syyyy-mm-dd hh24:mi:ss'))
9 - filter("TEST2"."DATE1">TO_DATE(' 1960-01-01 00:00:00',
'syyyy-mm-dd hh24:mi:ss'))
Note: cpu costing is off
27 rows selected.
ORA92080>/*
DOC>| Workaround: change the check constraint on the test1 table that is causing the problem.
DOC>*/
ORA92080>ALTER TABLE test1
2 DROP CONSTRAINT test1_chk_date2;
Table altered.
ORA92080>
ORA92080>ALTER TABLE test1
2 ADD ( CONSTRAINT test1_chk_date2
3      CHECK ( date2 >= date1 OR date2 IS NULL )
4      EXCEPTIONS INTO exceptions
5      );
Table altered.
ORA92080>
ORA92080>SELECT COUNT(*) FROM test1 t
2 WHERE EXISTS
3      ( SELECT 'X'
4      FROM ( SELECT id, date1
5                FROM test1
6           MINUS
7           SELECT id, date1
8                FROM test2
9           ) i
10      WHERE i.id = t.id
11           AND i.date1 = t.date1
12      );
COUNT(*)
2
1 row selected.
ORA92080>
ORA92080>EXPLAIN PLAN FOR
2 SELECT COUNT(*) FROM test1 t
3 WHERE EXISTS
4      ( SELECT 'X'
5      FROM ( SELECT id, date1
6                FROM test1
7           MINUS
8           SELECT id, date1
9                FROM test2
10           ) i
11      WHERE i.id = t.id
12           AND i.date1 = t.date1
13      );
Explained.
| Id | Operation | Name | Rows | Bytes | Cost |
| 0 | SELECT STATEMENT | | 1 | 44 | 11 |
| 1 | SORT AGGREGATE | | 1 | 44 | |
|* 2 | HASH JOIN SEMI | | 1 | 44 | 11 |
| 3 | TABLE ACCESS FULL | TEST1 | 409 | 8998 | 2 |
| 4 | VIEW | | 20 | 440 | 8 |
| 5 | MINUS | | | | |
| 6 | SORT UNIQUE | | 20 | 440 | |
|* 7 | TABLE ACCESS FULL| TEST1 | 20 | 440 | 2 |
| 8 | SORT UNIQUE | | 1 | 22 | |
|* 9 | TABLE ACCESS FULL| TEST2 | 1 | 22 | 2 |
Predicate Information (identified by operation id):
2 - access("I"."ID"="T"."ID" AND "I"."DATE1"="T"."DATE1")
7 - filter("TEST1"."DATE1">TO_DATE(' 1960-01-01 00:00:00',
'syyyy-mm-dd hh24:mi:ss'))
9 - filter("TEST2"."DATE1">TO_DATE(' 1960-01-01 00:00:00',
'syyyy-mm-dd hh24:mi:ss'))
Note: cpu costing is off
26 rows selected.
ORA92080>

Justin,
Thanks for the reply. I have sent this test case to my DBA who may submit it to Metalink.
Since I have found and implemented a workaround, I can wait for the next service release. I just thought that this might be of interest to other Oracle users.
My work-around (buried near the end of my original post) was to modify all check constraints that fit the pattern:
( not_nullable_column condition IS TRUE )
AND ( nullable_column condition IS TRUE )
To:
( not_null_column condition IS TRUE )
AND ( nullable_column condition IS TRUE OR nullable_column IS NULL )
Redefining a check constraint in this way prevents it from being used in the optimizer's predicate.
If someone at Oracle Support wanted to submit code that identifies such potential problem constraints in the data dictionary, that would be great too.
- Doug

RDBMS Version 8.0.5.0.0 Start시 mount 상태로 있어요.

alert 로그 파일을 보면 아래와 같이 마지막 부분에 alter database mount 상태로 있습니다..
db를 mount 후 open 하고 싶습니다.
방법이 없나요...
Wed Aug 12 17:47:01 2009
Shutting down instance (abort)
License high water mark = 3
Instance terminated by USER, pid = 9937
Wed Aug 12 17:50:12 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
LICENSE_MAX_USERS = 0
Starting up ORACLE RDBMS Version: 8.0.5.0.0.
System parameters with non-default values:
tracefiles_public = TRUE
processes = 150
event = 10210 trace name context forever, level 2, 10211 trace name context forever, level 2, 10235 trace name context forever, level 1, 10246 trace name context forever, level 2, 7267 trace name errorstack level 4, 3106 trace name errorstack level 4, 10076 trace name context forever, level 1
shared_pool_size = 128000000
enqueue_resources = 5000
nls_language = american
nls_territory = america
nls_sort = binary
nls_date_format = DD-MON-RR
nls_numeric_characters = .,
control_files = /d01/oradata/PRD/cntrl01.ctl
db_block_buffers = 500
db_block_size = 8192
log_buffer = 327680
log_checkpoint_interval = 10000
db_files = 200
db_file_multiblock_read_count= 32
dml_locks = 500
row_locking = always
rollback_segments = RBS01, RBS02, RBS03, RBS04, RBS05, RBS06, RBS07
sequence_cache_entries = 100
sequence_cache_hash_buckets= 89
sort_area_size = 256000
db_name = PRD
open_cursors = 255
optimizerundo_changes = TRUE
optimizer_mode = rule
utl_file_dir = /usr/tmp, /d01/app/applmgr/1103/common/TMP, /d01/app/applmgr/1103/ja/11.0.28/out
background_dump_dest = /d01/app/oracle/admin/PRD/bdump
user_dump_dest = /d01/app/oracle/admin/PRD/udump
max_dump_file_size = 10240
core_dump_dest = /d01/app/oracle/admin/PRD/cdump
aq_tm_processes = 1
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
QMN0 started with pid=8
Wed Aug 12 17:50:13 2009
alter database mount

장애 상황으로 open이 안되는 건지 아니면 startup mount를 통한 startup인지 구분이 필요하겠지만
만약 장애 상황이 아니라면
alter database open;
명령어로 mount 단계에서 open 단계로 넘어갈 수 있습니다.
만약 장애 상황에 따른 open 불가 상황이라면 장애를 복구하는 방향으로 접근해야 합니다.

Is XML DB versions tied to RDBMS versions?

Hi,
Can new functionality of XML DB be deployed to older versions of a database? I currently have RDBMS version of 92060 (yes, old, and yes it's Oracle EBS)
Is it possible to install 10g XML DB functionality into this database? without first upgrading to 10g?
Regards,
Alex

9.2.0.6.0 can provide 9.2.0.6.0 XML DB functionality. If XML DB is not enabled it can be enabled by running catqm. However since XML DB functionality is native to the database and tightly integrated with the kernel you cannot install functionality that was introduced in a later release of the database.

Cannot determine Oracle RDBMS version.

HI,
i am trying to install oracle patch 'SAP11203V3P_1402-20009981.ZIP' while executing the installation i am geeting following error.
kindly advise.
or if possible to share the steps to apply the patch. my SAP ECC 6 EHP7 installation got stuck.
Regards
Sunil

Hi Sunil,
As per analysis of second screenshot please confirm me a point :
1.For the installation of oracle 11g you used to go /oracle/stage/112_64/database/SAP/ through user ora<sid> .Here please clarify me have you set any environment variable except display variable before execution of ./RUNINSTALLER (Means please unset LD_LIBRARY_PATH,ORACLE_PATH etc if you did).
For successful installation first use to set environment variable xhost + from the root terminal & switch to su - ora<sid> and on this terminal don't set any other environment variable like LD_LIBRARY_PATH,ORACLE_PATH etc.Please do a clean installation of ORACLE 11G w/t setting any variables except display parameter.
Hope this will help you.
Regards,
Gaurav

Java API's supported in the Jdeveloper, IAS, and RDBMS product components

If there are any technical errors or "mistatement of the facts" in this posting, please let me know about them ..
This article is being delivered in Draft form and may contain
errors. Please use the MetaLink "Feedback" button to advise
Oracle of any issues related to this article.
PURPOSE
This article describes the "Enterprise Java Beans" (EJB), "Java Server Pages"
(JSP) and servlets Application Programming Interfaces (API) supported by the
Oracle products, Jdeveloper, Internet Application Server (IAS) and the Oracle
RDBMS release 2 and release 3, also known as Version 8.1.6 and 8.1.7,
respectively.
SCOPE & APPLICATION
All parties interested in the Java API's supported by these products.
Java API's supported in the Jdeveloper, IAS, and RDBMS product components
JDEVELOPER
JDEVELOPER is Oracle's Java development tool designed for coding / development,
testing / debugging, and deployment of Java Applications to the IAS and
RDBMS platforms.
With the java software api's being in a constant state of evolution, each new
release of Jdeveloper adds support for the "then current" version of the java
software api's, if it does not already have it implemented.
JDEVELOPER SERVLET API JSP API EJB API
VERSION VERSION VERSION VERSION
3.2.X.X 2.2 1.1 1.1
3.1.X.X 2.1 1.0 1.0
NOTE :
Sun Microsystems and their advisory teams (Oracle is on it) is working on
"draft" specifications for the next version of all of these API's
EJB -------> http://java.sun.com/products/ejb/index.html
JSP -------> http://java.sun.com/products/jsp/index.html
Servlets --> http://java.sun.com/products/servlet/?frontpage-javaplatform
It is anticipated that future releases of Jdeveloper will continue to be
upgraded to include support for the next version of each api.
To obtain the latest information on Oracle's Internet Development Suite (IDS)
of tools, please review the "Internet Developer Suite" information located
on Oracle's technet web site at :
http://technet.oracle.com/products/index.htm
IAS
IAS is Oracle's next evolution of the web server and application server
product technology superceeding the Web Application Server (WAS) and Oracle
Application Server (OAS) product lines.
IAS SERVLET API JSP API EJB API EJE VERSION
VERSION VERSION VERSION VERSION SUPPORTED
9I(1.0.2) 2.2 1.1 1.1 817
8i(1.0.1-NT) 2.0 1.0 1.0 816
8i(1.0.0-UNIX) 2.0 1.0 1.0 816
The IAS product contains two Java Virtual Machines (JVM) within it's
architecture.
They are called :
1) APACHE JSERV servlet engine
2) ORACLE ENTERPRISE JAVA ENGINE (EJE)
APACHE JSERV servlet engine
The APACHE JSERV servlet engine is an EXISTING product licensed from the
apache group which supports the servlet api 2.0.ONLY.
The APACHE JSERV product does not support ANY JSP's unless the customer
installs a third party jsp engine.
The IAS 8i/9i which has the APACHE JSERV product embedded in it, comes with
Oracle's JSP engine (OJSP) already integrated into it. OJSP supports JSP's up
to the specific JSP engine version documented in the Oracle Universal
Installer (OUI) for the 8.1.7 RDBMS or the IAS products. It is also documented
in the product's release notes.
Oracle ENTERPRISE JAVA ENGINE (EJE)
The EJE formerly known as :
1) Oracle 8i Java Virtual Machine (JVM)
2) JSERVER component,
3) Aurora JVM
was originally releas ed in the RDBMS 8.1.5 database with jdk 1.1.6 based java
support.
The currently supported versions of the Oracle 8i RDBMS, versions 2 and 3,
also known as Version 8.1.6 and 8.1.7, respectively, provides a jdk 1.2.1
based java virtual machine support.
"EJE" Version 816
This EJE, found in rdbms 8.1.6 and IAS 8i, contains support for the ejb
api 1.0, corba, and java stored procedures.
"EJE" Version 817
This EJE, found in rdbms 8.1.7 and IAS 9i, contains support for the ejb,
corba, and java stored procedures as well as the Oracle Servlet Engine (OSE)
which provides support for the servlets 2.2 api and JSP 1.1 api.
Note :
EJB support in the "EJE" Version 817 has been upgraded to comply with the EJB
1.1 api specification which includes "entity beans" support.
What is the bottom line ??
1) Servlets deployed to the APACHE JSERV must comply with servlet api 2.0.
2) Servlets 2.1 or higher are only supported in EJE's OSE component found in
the rdbms 817 or ias 9i products. Servlets api 2.0 can also run in the OSE.
References
1) "Oracle9i Application Server Technical White Paper" located at :
http://technet.oracle.com/products/ias/pdf/9ias_102.pdf
2) "Whats New? Oracle8i JVM Accelerator, Oracle Servlet Engine, OracleJSP ..."
located at :
http://technet.oracle.com/products/oracle8i/pdf/504.pdf
3) "Oracle8i Release 3 New Features Summary" located at :
http://technet.oracle.com/products/oracle8i/pdf/8iR3_nfs.pdf
null

which jvm is used by jserv ?? EJE or a separate jdk ?
The Jserv servlet engine is running in a separate jdk JVM external to the EJE jvm which is embedded within the "database" component of ias and the RDBMS.
See the reference below for more details ...
if jserv only support old apis, why it is in oracle's products ?
i would assume that the oracle servlet engine was under development when ias 8i was released and became available in time for the ias 9i and rdbms 817 products.
looking back in history leads me to believe ias 8i was a migration path to get to ias 9i or rdbms 817.
Based upon the long history of new releases of every oracle product being upgraded with new features, it's reasonable to assume that these products will continue to evolve.
when I deploy a jsp how to deploy in the right servlet container ("EJE") ?
as documented in the reference below, you can deploy JSP's to either the apache jserv jvm or the EJE since the ORACLE JSP engine functionality is in both jvm's.
there are many posts where you can see that people have deploy in jserv and they have problems because they don't use the right container (servlet 2.0 instead of
servlet 2.2) http://technet.oracle.com:89/ubb/Forum2/HTML/006349.html
when ias 8i came out this was clearly an issue since servlet support was at api 2.0, and the current servlet api was probably at 2.1.
oracle clearly made every effort to get ias 9i released quickly to supply a servlet 2.1 and 2.2 capable engine to resolve this issue.
since ias 9i and rdbms 8.1.7 are available this is no longer an issue.
The reference below explains the architecture and understanding it would eliminate a lot of "deploy to the wrong ias 9i component" issues.
so why jserv is bundled with oracle 8i/9ias since EJE support the right api version ?
if in ias 9i release , oracle had removed the jserv component without any advance warning, many customers would have been very upset since oracle makes every attempt to give advance notice before removal of functionality.
References
1) "Oracle9i Application Server Technical White Paper" located at :
http://technet.oracle.com/products/ias/pdf/9ias_102.pdf

DG4MSQL version 11.2.0.3.0, any query results in 'got native error 1007'

I installed Oracle Gateway for MSSQL version 11.2.0.3.0 to a separate Oracle Home (platform is IBM AIX 6.1 64-bit). After setting up listener, init.ora file etc., I created database link and tried few queries (database version 11.2.0.2.0 with patches 12827726, 12827731 applied). All queries result in error message:
SQL> select count(*) from s4user@imosprodnew;
select count(*) from s4user@imosprodnew
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Oracle][ODBC SQL Server Legacy Driver]20450 {20450}[Oracle][ODBC SQL Server Legacy Driver][SQL Server]Changed language setting to us_english.
{01000,NativeErr = 5703}[Oracle][ODBC SQL Server Legacy Driver][SQL Server]Changed database context to 'imosprod'. {01000,NativeErr = 5701}
[Oracle][ODBC SQL Server Legacy Driver][SQL Server]The number '042100421004210042110421104211042190421904219' is out of the range for numeric
representation (maximum precision 38). {22003,NativeErr = 1007}[Oracle][ODBC SQL Server Legacy Driver][SQL Server]Incorrect syntax near
'042100421004210042110421104211042190421904219'. {10103,NativeErr = 102}
ORA-02063: preceding 3 lines from IMOSPRODNEW
Trace file shows:
Heterogeneous Agent Release
11.2.0.3.0
ODBCINST set to "/app/oragw/product/11.2.0.3/dg4msql/driver/dg4msql.loc"
RC=-1 from HOSGIP for "LIBPATH"
LIBPATH from environment is "/app/oragw/product/11.2.0.3/dg4msql/driver/lib:/app/oragw/product/11.2.0.3/lib"
Setting LIBPATH to "/app/oragw/product/11.2.0.3/dg4msql/driver/lib:/app/oragw/product/11.2.0.3/dg4msql/driver/lib:/app/oragw/product/11.2.0.3/lib"
HOSGIP for "HS_FDS_SHAREABLE_NAME" returned "/app/oragw/product/11.2.0.3/dg4msql/driver/lib/odbc.so"
treat_SQLLEN_as_compiled = 1
uencoding=UTF8
##>Connect Parameters (len=226)<##
## DRIVER=Oracle 11g dg4msql;
## Address=10.1.0.20\IMOS;
## Database=imosprod;
#! UID=IMOS;
#! PWD=*
## AnsiNPW=Yes;
## EnableQuotedIdentifiers=1;
## IANAAppCodePage=2252;
## OctetSizeCalculation=1;
## PadVarbinary=0;
## SupportNumericPrecisionGreaterThan38=1;
Exiting hgogenconstr, rc=0 at 2013/06/06-14:54:21
Entered hgopoer at 2013/06/06-14:54:21
hgopoer, line 231: got native error 0 and sqlstate 20450; message follows...
[Oracle][ODBC SQL Server Legacy Driver]20450 {20450}[Oracle][ODBC SQL Server Legacy Driver][SQL Server]Changed language setting to us_english. {01000
,NativeErr = 5703}[Oracle][ODBC SQL Server Legacy Driver][SQL Server]Changed database context to 'imosprod'. {01000,NativeErr = 5701}
Exiting hgopoer, rc=0 at 2013/06/06-14:54:21
hgocont, line 2688: calling SqlDriverConnect got sqlstate 20450
DriverName:HGmsss23.so, DriverVer:06.11.0052 (b0047, U0046)
DBMS Name:Microsoft SQL Server, DBMS Version:10.00.4000
Entered hgopoer at 2013/06/06-14:54:21
hgopoer, line 231: got native error 1007 and sqlstate 22003; message follows...
[Oracle][ODBC SQL Server Legacy Driver][SQL Server]The number '042100421004210042110421104211042190421904219' is out of the range for numeric represe
ntation (maximum precision 38). {22003,NativeErr = 1007}[Oracle][ODBC SQL Server Legacy Driver][SQL Server]Incorrect syntax near '0421004210042100421
10421104211042190421904219'. {10103,NativeErr = 102}
Exiting hgopoer, rc=0 at 2013/06/06-14:54:21
hgoulcp, line 1932: calling SQLGetTypeInfo got sqlstate 22003
Exiting hgoulcp, rc=28500 at 2013/06/06-14:54:21 with error ptr FILE:hgoulcp.c LINE:1932 ID:SQLGetTypeInfo: LONGVARCHAR
hostmstr: 349326: RPC After Upload Caps
hostmstr: 349326: RPC Before Exit Agent
hostmstr: 349326: HOA Before hoalgof
Entered hgolgof at 2013/06/06-14:54:21
tflag:0
Entered hgopoer at 2013/06/06-14:54:21
hgopoer, line 231: got native error 0 and sqlstate 20131; message follows...
[Oracle][ODBC SQL Server Legacy Driver]20131 {20131}
Exiting hgopoer, rc=0 at 2013/06/06-14:54:21
hgolgof, line 180: calling SQLDisconnect got sqlstate 20131
Exiting hgolgof, rc=28500 at 2013/06/06-14:54:21 with error ptr FILE:hgolgof.c LINE:180 ID:Disconnect
hostmstr: 349326: HOA After hoalgof
hostmstr: 349326: HOA Before hoaexit
Entered hgoexit at 2013/06/06-14:54:21
Entered hgopoer at 2013/06/06-14:54:21
hgopoer, line 231: got native error 0 and sqlstate HY010; message follows...
[DataDirect][ODBC lib] Function sequence error {HY010}
Exiting hgopoer, rc=0 at 2013/06/06-14:54:21
hgoexit, line 126: calling SQLFreeHandle got sqlstate HY010
Exiting hgoexit, rc=0 with error ptr FILE:hgoexit.c LINE:126 ID:Free ENV handle
hostmstr: 349326: HOA After hoaexit
hostmstr: 349326: RPC After Exit Agent
Could this be some sort of incompatibility between DG4MSQL version 11.2.0.3.0 and RDBMS version 11.2.0.2.0?
I did not find anything relevant by searching, really (apart from one thread suggesting that this could be caused by misconfigured Linux OS, but my platform is AIX)

I created test table and inserted data (using FreeTDS tsql tool):
locale is "en_US.UTF-8"
locale charset is "UTF-8"
1> use imosprod
2> go
1> create table TEST_MSSQL (PKEY integer, DATA varchar(20))
2> go
1> insert into TEST_MSSQL values (1000,'Data for key 1000')
2> go
1> insert into TEST_MSSQL values (2000,'Data for key 2000')
2> go
1> select * from TEST_MSSQL
2> go
PKEY    DATA
1000    Data for key 1000
2000    Data for key 2000
(2 rows affected)
Then, I queried test table with:
1) DG4ODBC 11.2.0.2 + IBM-branded DataDirect ODBC driver,
2) DG4MSQL 11.2.0.2 and
3) DG4MSQL 11.2.0.3
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning and Automatic Storage Management options
SQL> select * from test_mssql@imos;
      PKEY DATA
========== ====================
      1000 Data for key 1000
      2000 Data for key 2000
SQL> select * from test_mssql@imosprod;
      PKEY DATA
========== ====================
      1000 Data for key 1000
      2000 Data for key 2000
SQL> select * from test_mssql@imosprodnew;
select * from test_mssql@imosprodnew
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Oracle][ODBC SQL Server Legacy Driver]20450 {20450}[Oracle][ODBC SQL Server
Legacy Driver][SQL Server]Changed language setting to us_english.
{01000,NativeErr = 5703}[Oracle][ODBC SQL Server Legacy Driver][SQL
Server]Changed database context to 'imosprod'. {01000,NativeErr = 5701}
[Oracle][ODBC SQL Server Legacy Driver][SQL Server]The number
'042100421004210042110421104211042190421904219' is out of the range for numeric
representation (maximum precision 38). {22003,NativeErr = 1007}[Oracle][ODBC
SQL Server Legacy Driver][SQL Server]Incorrect syntax near
'042100421004210042110421104211042190421904219'. {10103,NativeErr = 102}
ORA-02063: preceding 3 lines from IMOSPRODNEW
Seems to be a change in internal logic of DG4MSQL in version 11.2.0.3 to me.

Oracle XE Western version not working on Windows XP pro

I have noticed that production version of the Oracle XE Western version does not work properly. The beta version created the database properly, the production version does not. I tried to install it on a Windows XP Pro version.
Below is the alert_xe.log
Dump file c:\oracle\xeprod\app\oracle\admin\xe\bdump\alert_xe.log
Thu Mar 30 11:38:32 2006
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 2
CPU : 1 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:533M/1023M, Ph+PgF:2253M/2461M, VA:1945M/2047M
Thu Mar 30 11:38:32 2006
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Shared memory segment for instance monitoring created
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
sessions = 49
sga_target = 285212672
control_files = C:\ORACLE\XEPROD\ORADATA\XE\CONTROL.DBF
compatible = 10.2.0.1.0
db_recovery_file_dest = C:\oracle\xeprod\app\oracle\flash_recovery_area
db_recovery_file_dest_size= 10737418240
undo_management = AUTO
undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
shared_servers = 4
job_queue_processes = 4
audit_file_dest = C:\ORACLE\XEPROD\APP\ORACLE\ADMIN\XE\ADUMP
background_dump_dest = C:\ORACLE\XEPROD\APP\ORACLE\ADMIN\XE\BDUMP
user_dump_dest = C:\ORACLE\XEPROD\APP\ORACLE\ADMIN\XE\UDUMP
core_dump_dest = C:\ORACLE\XEPROD\APP\ORACLE\ADMIN\XE\CDUMP
db_name = XE
open_cursors = 300
os_authent_prefix =
pga_aggregate_target = 94371840
MMAN started with pid=4, OS id=4092
PSP0 started with pid=3, OS id=4088
PMON started with pid=2, OS id=4084
DBW0 started with pid=5, OS id=2044
LGWR started with pid=6, OS id=1248
CKPT started with pid=7, OS id=200
SMON started with pid=8, OS id=2036
RECO started with pid=9, OS id=2012
CJQ0 started with pid=10, OS id=212
MMON started with pid=11, OS id=1924
Thu Mar 30 11:38:38 2006
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=380
Thu Mar 30 11:38:38 2006
starting up 4 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Thu Mar 30 11:38:42 2006
The input backup piece C:\ORACLE\XEPROD\APP\ORACLE\PRODUCT\10.2.0\SERVER\CONFIG\SEEDDB\EXPRESS.DFB is in compressed format.
Thu Mar 30 11:39:10 2006
Full restore complete of datafile 4 to datafile copy C:\ORACLE\XEPROD\ORADATA\XE\USERS.DBF. Elapsed time: 0:00:26
checkpoint is 193065
Full restore complete of datafile 2 to datafile copy C:\ORACLE\XEPROD\ORADATA\XE\UNDO.DBF. Elapsed time: 0:00:27
checkpoint is 193065
Thu Mar 30 11:39:27 2006
Full restore complete of datafile 3 to datafile copy C:\ORACLE\XEPROD\ORADATA\XE\SYSAUX.DBF. Elapsed time: 0:00:45
checkpoint is 193065
Thu Mar 30 11:39:27 2006
Errors in file c:\oracle\xeprod\app\oracle\admin\xe\udump\xe_ora_488.trc:
ORA-00600: internal error code, arguments: [krbrckhr_fail], [C:\ORACLE\XEPROD\APP\ORACLE\PRODUCT\10.2.0\SERVER\CONFIG\SEEDDB\EXPRESS.DFB], [83], [128], [3], [9427], [], []
Thu Mar 30 11:39:29 2006
Create controlfile reuse set database "XE"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'C:\oracle\xeprod\oradata\XE\system.dbf',
'C:\oracle\xeprod\oradata\XE\undo.dbf',
'C:\oracle\xeprod\oradata\XE\sysaux.dbf',
'C:\oracle\xeprod\oradata\XE\users.dbf'
LOGFILE
GROUP 1 SIZE 51200K,
GROUP 2 SIZE 51200K,
RESETLOGS
Thu Mar 30 11:39:29 2006
WARNING: Default Temporary Tablespace not specified in CREATE DATABASE command
Default Temporary Tablespace will be necessary for a locally managed database in future release
Thu Mar 30 11:39:29 2006
Errors in file c:\oracle\xeprod\app\oracle\admin\xe\udump\xe_ora_744.trc:
ORA-01565: error in identifying file 'C:\oracle\xeprod\oradata\XE\system.dbf'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-1503 signalled during: Create controlfile reuse set database "XE"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'C:\oracle\xeprod\oradata\XE\system.dbf',
'C:\oracle\xeprod\oradata\XE\undo.dbf',
'C:\oracle\xeprod\oradata\XE\sysaux.dbf',
'C:\oracle\xeprod\oradata\XE\users.dbf'
LOGFILE
GROUP 1 SIZE 51200K,
GROUP 2 SIZE 51200K,
RESETLOGS...
Shutting down instance: further logons disabled
Thu Mar 30 11:39:29 2006
Stopping background process CJQ0
Thu Mar 30 11:39:29 2006
Stopping background process MMNL
Thu Mar 30 11:39:29 2006
Stopping background process MMON
Thu Mar 30 11:39:30 2006
Shutting down instance (immediate)
License high water mark = 1
Thu Mar 30 11:39:30 2006
Stopping Job queue slave processes
Thu Mar 30 11:39:30 2006
Job queue slave processes stopped
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Thu Mar 30 11:39:32 2006
ALTER DATABASE CLOSE NORMAL
ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thu Mar 30 11:39:34 2006
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
sessions = 49
sga_target = 285212672
control_files = C:\ORACLE\XEPROD\ORADATA\XE\CONTROL.DBF
compatible = 10.2.0.1.0
db_recovery_file_dest = C:\oracle\xeprod\app\oracle\flash_recovery_area
db_recovery_file_dest_size= 10737418240
undo_management = AUTO
undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
shared_servers = 4
audit_file_dest = C:\ORACLE\XEPROD\APP\ORACLE\ADMIN\XE\ADUMP
background_dump_dest = C:\ORACLE\XEPROD\APP\ORACLE\ADMIN\XE\BDUMP
user_dump_dest = C:\ORACLE\XEPROD\APP\ORACLE\ADMIN\XE\UDUMP
core_dump_dest = C:\ORACLE\XEPROD\APP\ORACLE\ADMIN\XE\CDUMP
db_name = XE
open_cursors = 300
os_authent_prefix =
pga_aggregate_target = 94371840
PMON started with pid=2, OS id=756
PSP0 started with pid=3, OS id=796
MMAN started with pid=4, OS id=836
DBW0 started with pid=5, OS id=928
LGWR started with pid=6, OS id=152
CKPT started with pid=7, OS id=924
SMON started with pid=8, OS id=932
RECO started with pid=9, OS id=1212
MMON started with pid=10, OS id=1272
MMNL started with pid=11, OS id=1296
Thu Mar 30 11:39:35 2006
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 4 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Thu Mar 30 11:39:35 2006
Create controlfile reuse set database "XE"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'C:\oracle\xeprod\oradata\XE\system.dbf',
'C:\oracle\xeprod\oradata\XE\undo.dbf',
'C:\oracle\xeprod\oradata\XE\sysaux.dbf',
'C:\oracle\xeprod\oradata\XE\users.dbf'
LOGFILE
GROUP 1 SIZE 51200K,
GROUP 2 SIZE 51200K,
RESETLOGS
Thu Mar 30 11:39:35 2006
WARNING: Default Temporary Tablespace not specified in CREATE DATABASE command
Default Temporary Tablespace will be necessary for a locally managed database in future release
Thu Mar 30 11:39:35 2006
Errors in file c:\oracle\xeprod\app\oracle\admin\xe\udump\xe_ora_1144.trc:
ORA-01565: error in identifying file 'C:\oracle\xeprod\oradata\XE\system.dbf'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-1503 signalled during: Create controlfile reuse set database "XE"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'C:\oracle\xeprod\oradata\XE\system.dbf',
'C:\oracle\xeprod\oradata\XE\undo.dbf',
'C:\oracle\xeprod\oradata\XE\sysaux.dbf',
'C:\oracle\xeprod\oradata\XE\users.dbf'
LOGFILE
GROUP 1 SIZE 51200K,
GROUP 2 SIZE 51200K,
RESETLOGS...
Thu Mar 30 11:39:35 2006
Stopping background process MMNL
Thu Mar 30 11:39:36 2006
Stopping background process MMON
Starting background process MMON
Starting background process MMNL
MMON started with pid=10, OS id=580
MMNL started with pid=11, OS id=1288
Thu Mar 30 11:39:36 2006
ALTER SYSTEM enable restricted session;
Thu Mar 30 11:39:36 2006
alter database "XE" open resetlogs
ORA-1507 signalled during: alter database "XE" open resetlogs...
Thu Mar 30 11:39:36 2006
alter database drop logfile group 3
ORA-1507 signalled during: alter database drop logfile group 3...
Thu Mar 30 11:39:36 2006
ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\oracle\xeprod\oradata\XE\temp.dbf' SIZE 20480K REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
ORA-1109 signalled during: ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\oracle\xeprod\oradata\XE\temp.dbf' SIZE 20480K REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED...
Thu Mar 30 11:39:36 2006
ALTER SYSTEM disable restricted session;
Shutting down instance: further logons disabled
Thu Mar 30 11:39:37 2006
Stopping background process MMNL
Thu Mar 30 11:39:38 2006
Stopping background process MMON
Thu Mar 30 11:39:38 2006
Shutting down instance (immediate)
License high water mark = 1
Waiting for dispatcher 'D000' to shutdown
Waiting for shared server 'S000' to die
Waiting for shared server 'S002' to die
Waiting for shared server 'S003' to die
All dispatchers and shared servers shutdown
Thu Mar 30 11:39:39 2006
ALTER DATABASE CLOSE NORMAL
ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thu Mar 30 11:39:42 2006
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
sessions = 49
spfile = C:\ORACLE\XEPROD\APP\ORACLE\PRODUCT\10.2.0\SERVER\DBS\SPFILEXE.ORA
sga_target = 285212672
control_files = C:\ORACLE\XEPROD\ORADATA\XE\CONTROL.DBF
compatible = 10.2.0.1.0
db_recovery_file_dest = C:\oracle\xeprod\app\oracle\flash_recovery_area
db_recovery_file_dest_size= 10737418240
undo_management = AUTO
undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
shared_servers = 4
job_queue_processes = 4
audit_file_dest = C:\ORACLE\XEPROD\APP\ORACLE\ADMIN\XE\ADUMP
background_dump_dest = C:\ORACLE\XEPROD\APP\ORACLE\ADMIN\XE\BDUMP
user_dump_dest = C:\ORACLE\XEPROD\APP\ORACLE\ADMIN\XE\UDUMP
core_dump_dest = C:\ORACLE\XEPROD\APP\ORACLE\ADMIN\XE\CDUMP
db_name = XE
open_cursors = 300
os_authent_prefix =
pga_aggregate_target = 94371840
PMON started with pid=2, OS id=1480
PSP0 started with pid=3, OS id=1484
MMAN started with pid=4, OS id=1488
DBW0 started with pid=5, OS id=576
LGWR started with pid=6, OS id=1492
CKPT started with pid=7, OS id=1496
SMON started with pid=8, OS id=1260
RECO started with pid=9, OS id=376
CJQ0 started with pid=10, OS id=824
MMON started with pid=11, OS id=244
MMNL started with pid=12, OS id=1636
Thu Mar 30 11:39:42 2006
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 4 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Thu Mar 30 11:39:42 2006
ALTER DATABASE MOUNT
Thu Mar 30 11:39:42 2006
ORA-00202: control file: 'C:\ORACLE\XEPROD\ORADATA\XE\CONTROL.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Thu Mar 30 11:39:42 2006
ORA-205 signalled during: ALTER DATABASE MOUNT...
Thu Mar 30 11:41:54 2006
alter database mount
Thu Mar 30 11:41:54 2006
ORA-00202: control file: 'C:\ORACLE\XEPROD\ORADATA\XE\CONTROL.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-205 signalled during: alter database mount
Thanks,
Lucian

I think the relevant error from the log file is as follows
ORA-01565: error in identifying file 'C:\oracle\xeprod\oradata\XE\system.dbf'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-1503 signalled during: Create controlfile reuse set database "XE
There are a couple of things to consider here
Why is this install going into c:\oracle\xeprod ? If should be going into C:\oraclexe. Did you do something to change the default install infrastructure ?
Secondly - sometimes we see this unable to open file error message if some other process is reading the file at the same time as the installer is trying to install it. Anti virus software and Google desktop have been culprits to date.

Is oracle applications 11.5.10.2 certified with 11.1.0.7.7 version of datab

1) The oracle certification matrix just says that RDBMS version 11.1.0.7.0 is certified with 11.5.10.2 version of Oracle apps. I want to know if the PSU updates are also certified with oracle applications. For example is 11.1.0.7.7 (PSU update 7) also certified with 11.5.10.2?
2) What if we apply PSU patches to our 11.1.0.7.0 version of RDBMS? will it be supported? Please note that the verion of DB changes with the application of PSU patches
Thanks & Regards,
sree.

1) The oracle certification matrix just says that RDBMS version 11.1.0.7.0 is certified with 11.5.10.2 version of Oracle apps. I want to know if the PSU updates are also certified with oracle applications. For example is 11.1.0.7.7 (PSU update 7) also certified with 11.5.10.2? Yes.
Can E-Business Users Apply Database Patch Set Updates?
http://blogs.oracle.com/stevenChan/2009/08/can_ebs_users_apply_database_patch_set_updates.html
2) What if we apply PSU patches to our 11.1.0.7.0 version of RDBMS? will it be supported? Please note that the verion of DB changes with the application of PSU patchesYes -- Oracle Applications Release 11i with Oracle 11g Release 1 (11.1.0) [ID 452783.1]
Thanks,
Hussein

PSU level of RMAN Catalog DB version and Target DBs

Catalog DB Version: 11.2.0.2.3
Target DBs : 11.2.0.2.3
Currently our Catalog DB and Target DBs ( 15 of them) are of the same PSU level.
We are going to apply PSU 5 (11.2.0.2.3) on some of the target DBs . Should we apply PSU 5 (11.2.0.2.3) on the Catalog DB first before we apply this PSU on the target DBs?

Hi TeslaMan,
Probably you mean the rdbms version of the catalog is version 11.2.0.2.3.
If you upgrade target databases with a cpu you might need to upgrade the catalog schema to an equal or higher level.
Please check the current catalog schema version with the following sql.
select * from RCVER;Maybe you can create a dummy catalog schema with the patched up rdbms rman cli (maybe you tested the cpu already?) and check the new version with the same sql.
Regards,
Tycho

PRO*C VERSION MATRIX 및 VERSION 별 특성

제품 : PRECOMPILERS
작성날짜 : 1998-02-19
PRO*C version matrix 및 version 별 지원 내용
===========================================
[1] PRO*C 의 version 별 지원 내용
RDBMS 의 version 과 PRO*C 의 version 별 지원내용은 다음과 같다.
PRO*　　　　Last　　　　RDBMS　　　　Languages
Version　Version　Version
======================================================================
1.3　　　　　1.3.20　　<6.0.35　　　　　　PRO*C
1.4　　　　　1.4.15/6　6.x　　　　　　　　　　"
1.5　　　　　1.5.10　　　7.0.x　　　　　　　　"
1.6　　　　　1.6.7　　　　7.1.x　　　　　　　　"
1.6　　　　　1.6.9　　　　7.2.x　　　　　　　　"
2.0　　　　　2.0.6　　　　7.1.x　　　　　　　　"
2.1　　　　　2.1.3　　　　7.2.x　　　　　　　　"
2.2　　　　　2.2.?　　　　7.3.x　　　　　　　　"
[2] 각 version 의 pro*c의 precompile option 추가 부분과 header file
위치는 다음과 같다.
(1)　version　1.4
Location: $ORACLE_HOME/proc/demo
File: proc.mk
Build from "prog.pc":　　make -f proc.mk prog
Where to add options:　　edit PRO14FLAGS
Header files in:　　　　　　　$ORACLE_HOME/proc/lib
(2) version　1.5
Location: $ORACLE_HOME/proc/demo
File: proc.mk
Build from "prog.pc":　　make -f proc.mk prog
Where to add options:　　edit PROFLAGS
Header files in:　　　　　　　$ORACLE_HOME/proc/lib
(3) verion　1.6 , 1.7,1.8
Location: $ORACLE_HOME/proc16/demo
File: proc16.mk
Build from "prog.pc":　　make -f proc.mk prog
Where to add options:　　edit PCCFLAGS
Header files in:　　　　　　　$ORACLE_HOME/sqllib/public
(4) version 2.0, 2.1
Location: $ORACLE_HOME/proc/demo
File: proc.mk
Build from "prog1.pc":　make -f proc.mk EXE=prog OBJS="prog1.o prog2.o"
　　and "prog2.pc"
Where to add options:　　add PROFLAGS
Header files in:　　　　　　　$ORACLE_HOME/sqllib/public
(5) version 2.2
Location: $ORACLE_HOME/precomp/demo/proc
File: proc.mk
Build from "prog1.pc":　make -f proc.mk build EXE=prog OBJS="prog1.o
prog2.o"
　　and "prog2.pc"
Where to add options:　　add PROCFLAGS
Header files in:　　　　　　　$ORACLE_HOME/precomp/public
[3]다음은 각 VERSION 별 지원 내용을 살펴 보기로 한다.
(1) VERSION 1.4
1. precompiler option 의 추가된 부분은 LINES=YES option지정시 outpute 에
#line directives 생성 지원되어debugging 에 도움울 줄수 있게
되었으며, dynamic method 사용시 HOLD_CURSOR=YES option을 사용하여
cursor의 재사용을 방지할 수 있게 되었다. AREASIZE,REBIND option 이
없어지고 MODE=ANSI14 option 을 지원 가능하게 되었다. 그러나 이 ANSI14
option 을 사용시는 4byte inter 인 SQLCODE 를 반드시 declare 해야 한다.
SQLCHECK=SEMANTICS/SYNTAX/NONE (Default는 SYNTAX) 가 사용되고, 더이상
log를 db에 기록하지 않게 되었다.
2　　Datatype equivalencing 지원 한다.
　　　　EXEC SQL VAR　host_variable　IS datatype ;
　　　　EXEC SQL TYPE type is datatype　REFERENCE ;
3.　Indicator 변수를 사용가능 ( :host INDICATOR :indicator ) 하게
되었으며 또한 AT 절에 host 변수를 사용가능하게 되었다.　또host변수
선언시 auto, extern, static, const, volatile 사용 가능하다.
4.　SQLCA 의 sqlerrd(5) 에 0 based parse offset을 저장하였으나, v2.x 의
현재 version 에서는 사용되어지지　않고있다..
5　procedure call 이 가능하게 되었다. (EXEC SQL WHENEVER ... DO
procedure) .
　　또한　EXEC SQL WHENEVER ... DO break;　문이 사용가능하다 .
6.　Precompiler 실행모듈이 각 언어마다 구분되어 pro*c 의 경우function의
prototypes 생성
　　　가능하다.
(2) Version 1.5
============
이 version 은 ORACLE RDBMS 7.x 를 지원하는 pro*c version 으로 완벽한
ANSI SQL을 지원한다. 또한 NLS 의 support 도 지원가능하다
1.　precompile option 의 변경사항으로는　DBMS=NATIVE/V6/V7 option
지원하며 FIPS=YES로 설정시　ANSI extension 지원한다.
2.　　data type 변경사항으로는 fixed length datatypes 지원하는 CHARF,
CHARZ가 사용가능하며　LONG VARCHAR,LONG VARRAW datatypes 지원가능하다.
또한　MLSLABEL 데이타 타입사용 가능하게 되었는데 이는 variable_lengrh
의 binary OS label 을 저장할때 사용가능하다.
3.　indicators 없는 host 변수가 null을 fetch하면,　DBMS=V6으로
설정하지 않은 경우는
　　　ORA-1405를 return 함. PL/SQL table을 파라미터로 하는 stored
procedures 호출 가능.
4.　이전 version 에서 space 만 가능했던 (bug) input　character string
데이타 타입이
　　　terminator를 포함하는 경우도 이를 데이타로 인식 가능
(3)　version 1.6
==================
1.변경된 precompile option 으로　AUTO_CONNECT=YES option
지원하는데
이를 지정시는 처음 sql 문 수행시 OPS$<username>으로 자동 connect 된다.　
또한 CONFIG=<file> option 지원으로 user 의 configuration 의 name 과
위치를 지정할수 있다. 또한 시스템 config file 사용 가능한데 이의 위치는
UNIX = $ORACLE_HOME/proc16/pccc.cfg, VMS=ora_pcc:pccc.cfg. 이다.
2.　SQLSTATE 변수는 SQL문 실행 이후에 값이 설정된다. MODE=ANSI로 설정이
되어 있고, declare section안에 선언되어 있는 경우에만 이값이 설정된다.　
만일 그렇지 않으면 이 값은 무시된다.만약 SQLCODE가 안에 선언되어 있다면,
이 두 변수 모두 값이 설정된다.
　만약 SQLCODE가 밖에 선언되어 있다면 SQLSTATE만 설정된다. SQLSTATE는
coding scheme를 표준화하는데 사용된다. SQLCODE는　declare section
내부에 선언되거나, SQLSTATE, SQLCA가 사용되지 않는 경우에 사용하게 된다.
이 점은 1.5 버젼에서 SQLCA를 declare section 밖에 선언하여,　SQLCA와
같이 사용되었던 것과는 차이가 있다.
3.　SQLGLS 함수 지원하는데 이는 마지막 문장을 parse 한 후, 문장의 길이
및 타입을 return한다.　
eg)　int sqlgls(char *sqlstm ,size_t
*stmlen,size_t *sqlfc)
4.　select 문에서 stored function 을 call 할수 있다.
5.　단 SQLCHECK=FULL/SEMANTICS 가 아닌 경우에 FROM 절에서 subquery 가
가능하다. 이는 PL/SQL 의 semantic check 인 경우는 v7.3 에서 가능하다 .
(4) Version 1.8
================　
1.　INDICATOR VARIABLE을 사용하지 않고도 NULL FETCH시 ORA-1405 에러가
발생하지 않도록 UNSAFE_NULL=YES 옵션이 추가됨. UNSAFE_NULL=YES로
설정하면　ORA-1405 를 방지하기 위해서 DBMS=V6 으로 세팅할 필요없이
DBMS=V7 으로 할 수 있음. 단, UNSAFE_NULL=YES를 사용하기 위해서는
MODE=ORACLE 로 설정해야 함.
2.　PACKAGE ARGUMENT로 PL/SQL CURSOR(WEAKLY TYPED)를 사용할 수 있는데
예를 들면　TYPE GeneralCurTyp IS REF CURSOR;
3.　FROM 절에서 SUBQUERY를 사용할 수 있고 SQLCHECK=SEMANTICS 또는
SQLCHECK=FULL 옵션을 사용할 수 있음.
4.　PL/SQL 블럭에서 PL/SQL TABLE과 이와 관련된 다음 함수를 지원.
　a_table(index).EXISTS, a_table.COUNT, a_table.FIRST, a_table.LAST,
a_table.PRIOR(index), a_table.NEXT(index),
a_table.DELETE(start_index,_index), a_table.DELETE.
5. WHERE CURRENT OF CURSOR를 이용해서 MULTI-TABLE VIEW를 통해
KEY-PRESERVED TABLE을 UPDATE　가능.
(5)　version 2.0
==================
RDBMS version　7.3에서 부터　makefile 은
ins_precomp.mk,env_precomp.mk, proc.mk의 3 개로 나뉘었다.
Ins_precomp.mk 는 기존의 proc.mk 처럼 precompiler executables 를 build
하기 위한 routine 이고 env_precomp.mk 는 모든 environment 의 변수와
libraray 를 포함한다.
이 file 은 Ins_precomp.mk 와 proc.mk 에 포함되어 사용되어진다.
1.　V1.6과 같이 AUTO_CONNECT, CONFIG 옵션 지원. SYSTEM CONFIGURATION
FILE은 UNIX에서는 $ORACLE_HOME/proc/pmscfg.h 이고 VMS에서는
ora_proc20:pmscfg.cfg
2.　V1.6과 같이 SQLSTATE 변수와 SQLGLS 함수가 제공된다.
3.　C PREPROCESSOR가 포함되어서 #define이 EMBEDDED SQL과 함께 이용될 수
있고 #include 로 PRO*C 헤더화일을 INCLUDE 가능.
4.　구조체를 HOST 변수로 사용 가능.　이것은 SELECT INTO, FETCH INTO　
또는 INSERT시 VALUES 절에 사용될 수 있으나 PL/SQL PROCEDURE에 PL/SQL
RECORD ARGUMENT로 사용할 수는 없음.　구조체 내에 또다른 구조체를 포함할
수는 없지만　ARRAY는 포함할 수 있음.
5.　HOST 변수를 BEGIN/END DECLARE SECTION 안에 넣을 필요가 없음.
6.　V1.6에서 처럼 SELECT LIST에 STORED FUNCTION의 사용이 가능.
7.　SQLCHECK=FULL/SEMANTOCS를 사용하지 않는 경우 FROM 절에 SUBQUERY를
쓸 수 있음.
8.　CHARACTER 변수의 BIND TYPE은 MODE 옵션이 아니라 DBMS 옵션에 따라서
결정됨.　DBMS=V6/V6_CHAR 인 경우, CHARACTER는 TYPE 1, DBMS=V7(또는
NATIVE이고 ORACLE7에 접속할 때) 에서는 TYPE 97.
9.　DBMS=V6_CHAR 는 CHARACTER 변수가 가변 길이 문자열로 다루어질 수
있도록 함.
10.　SQLVCP 함수는 VARCHAR ARR 변수를 지정한 길이로 만들어 주므로
VARCHAR를 동적으로 할당할 때 COMPILER가 BYTE ALIGNMENT를 가능하게 함.
11.　PRO*C의 PARSE LEVEL을 설정하는 PARSE 옵션.
a)　NONE - PRO*C V1과 같음(HOST 변수를 DECLARE SECTION에 넣어야 함.
#define 인식 안함 등)
b)　PARTIAL - HOST 변수를 DECLARE SECTION에 넣어야 함
c)　FULL - PRO*C V2의 기능 모두 지원
12.　EXEC SQL WHENEVER ... DO 함수명(args,...); 와 같이 함수호출시UMENT를
주고 받을 수 있음.
13.　#ifdef/#ifndef 와 EXEC ORACLE IFDEF/IFNDEF 에서 사용하기 위한
DEFINE 옵션 지원.
(6) version 2.1
================
1.　PRO*C V1.7에서와 같이 char와 IMPLICIT VARCHAR (VARCHAR=YES 옵션과
함께 적절한 C 구조체로 선언된 변수) HOST 변수에서 MULTI-BYTE NLS
CHARACTER 데이타와 MULTI-BYTE 문자열을 지원.
　NLS_CHAR=var1,var2,... 옵션으로 MULTI-BYTE HOST 변수를 지정함.
MULTI-BYTE 리터럴은 다음과 같이 사용된다.
　EXEC SQL SELECT ... WHERE ENAME = N*이경구*;
　단, 이것은 SQLLIB RUNTIME LIBRARY를 통해서 지원되기 때문에 MULTI-BYTE
NLS 문자열은 DYNAMIC SQL에서 사용될 수 없음. NCHAR 데이타타입은 DDL 과
함께 사용될 수 없음.
2.　PRO*C V1.7과 같이 NLS_LOCAL 옵션 지원
3.　DEF_SQLCODE=YES 로 설정하면 PRO*C는 다음 문장을 생성한다.
　#define SQLCODE sqlca.sqlcode
　SQLCA는 반드시 INCLUDE 되어야 하며 SQLCODE 변수는 선언되어서는 안됨.
4.　PRO*C V1.7 과 같이 CURSOR VARIABLE 지원.
5.　VARCHAR=YES 로 설정하면 특정한 구조체를 VARCHAR로 인식할 수 있다.　
구조체의 형태를 보면
　struct
　short len;
　char arr[n];
　} host_var;
6.　CODE=CPP 로 설정하면 SQLLIB 함수 원형(PROTOTYPE)은 다음과 같이
extern "C" 형식으로 생성됨.
　extern "C" {
　void sqlora( unsigned long *, void *);
　그리고 "//" 와 같은 COMMENT 처리명령을 인식함. 단, CODE=CPP인 경우
PARSE 는 자동적으로 PARTIAL로 설정됨.
　CPP_SUFFIX 옵션은 PRECOMPILE된 화일의 확장자를 지정.
SYS_INCLUDE=(dir1,dir2,...) 옵션은 C 헤더 화일과 다른 위치에 있는 C++
헤더 화일이 있는 디렉토리를 지정. 이 옵션은 PARSE 옵션이 NONE이 아닌
경우에만 필요하다. HEADER 화일을 찾는 위치는 SYS_INCLUDE, 현재 디렉토리,
표준 SYSTEM 디렉토리(UNIX에서 PRO*C 헤더 화일의 위치는
$ORACLE_HOME/sqllib/public), 그리고 INCLUDE 옵션에 지정된 디렉토리이다.

제품 : PRECOMPILERS
작성날짜 : 1998-02-19
PRO*C version matrix 및 version 별 지원 내용
===========================================
[1] PRO*C 의 version 별 지원 내용
RDBMS 의 version 과 PRO*C 의 version 별 지원내용은 다음과 같다.
PRO*　　　　Last　　　　RDBMS　　　　Languages
Version　Version　Version
======================================================================
1.3　　　　　1.3.20　　<6.0.35　　　　　　PRO*C
1.4　　　　　1.4.15/6　6.x　　　　　　　　　　"
1.5　　　　　1.5.10　　　7.0.x　　　　　　　　"
1.6　　　　　1.6.7　　　　7.1.x　　　　　　　　"
1.6　　　　　1.6.9　　　　7.2.x　　　　　　　　"
2.0　　　　　2.0.6　　　　7.1.x　　　　　　　　"
2.1　　　　　2.1.3　　　　7.2.x　　　　　　　　"
2.2　　　　　2.2.?　　　　7.3.x　　　　　　　　"
[2] 각 version 의 pro*c의 precompile option 추가 부분과 header file
위치는 다음과 같다.
(1)　version　1.4
Location: $ORACLE_HOME/proc/demo
File: proc.mk
Build from "prog.pc":　　make -f proc.mk prog
Where to add options:　　edit PRO14FLAGS
Header files in:　　　　　　　$ORACLE_HOME/proc/lib
(2) version　1.5
Location: $ORACLE_HOME/proc/demo
File: proc.mk
Build from "prog.pc":　　make -f proc.mk prog
Where to add options:　　edit PROFLAGS
Header files in:　　　　　　　$ORACLE_HOME/proc/lib
(3) verion　1.6 , 1.7,1.8
Location: $ORACLE_HOME/proc16/demo
File: proc16.mk
Build from "prog.pc":　　make -f proc.mk prog
Where to add options:　　edit PCCFLAGS
Header files in:　　　　　　　$ORACLE_HOME/sqllib/public
(4) version 2.0, 2.1
Location: $ORACLE_HOME/proc/demo
File: proc.mk
Build from "prog1.pc":　make -f proc.mk EXE=prog OBJS="prog1.o prog2.o"
　　and "prog2.pc"
Where to add options:　　add PROFLAGS
Header files in:　　　　　　　$ORACLE_HOME/sqllib/public
(5) version 2.2
Location: $ORACLE_HOME/precomp/demo/proc
File: proc.mk
Build from "prog1.pc":　make -f proc.mk build EXE=prog OBJS="prog1.o
prog2.o"
　　and "prog2.pc"
Where to add options:　　add PROCFLAGS
Header files in:　　　　　　　$ORACLE_HOME/precomp/public
[3]다음은 각 VERSION 별 지원 내용을 살펴 보기로 한다.
(1) VERSION 1.4
1. precompiler option 의 추가된 부분은 LINES=YES option지정시 outpute 에
#line directives 생성 지원되어debugging 에 도움울 줄수 있게
되었으며, dynamic method 사용시 HOLD_CURSOR=YES option을 사용하여
cursor의 재사용을 방지할 수 있게 되었다. AREASIZE,REBIND option 이
없어지고 MODE=ANSI14 option 을 지원 가능하게 되었다. 그러나 이 ANSI14
option 을 사용시는 4byte inter 인 SQLCODE 를 반드시 declare 해야 한다.
SQLCHECK=SEMANTICS/SYNTAX/NONE (Default는 SYNTAX) 가 사용되고, 더이상
log를 db에 기록하지 않게 되었다.
2　　Datatype equivalencing 지원 한다.
　　　　EXEC SQL VAR　host_variable　IS datatype ;
　　　　EXEC SQL TYPE type is datatype　REFERENCE ;
3.　Indicator 변수를 사용가능 ( :host INDICATOR :indicator ) 하게
되었으며 또한 AT 절에 host 변수를 사용가능하게 되었다.　또host변수
선언시 auto, extern, static, const, volatile 사용 가능하다.
4.　SQLCA 의 sqlerrd(5) 에 0 based parse offset을 저장하였으나, v2.x 의
현재 version 에서는 사용되어지지　않고있다..
5　procedure call 이 가능하게 되었다. (EXEC SQL WHENEVER ... DO
procedure) .
　　또한　EXEC SQL WHENEVER ... DO break;　문이 사용가능하다 .
6.　Precompiler 실행모듈이 각 언어마다 구분되어 pro*c 의 경우function의
prototypes 생성
　　　가능하다.
(2) Version 1.5
============
이 version 은 ORACLE RDBMS 7.x 를 지원하는 pro*c version 으로 완벽한
ANSI SQL을 지원한다. 또한 NLS 의 support 도 지원가능하다
1.　precompile option 의 변경사항으로는　DBMS=NATIVE/V6/V7 option
지원하며 FIPS=YES로 설정시　ANSI extension 지원한다.
2.　　data type 변경사항으로는 fixed length datatypes 지원하는 CHARF,
CHARZ가 사용가능하며　LONG VARCHAR,LONG VARRAW datatypes 지원가능하다.
또한　MLSLABEL 데이타 타입사용 가능하게 되었는데 이는 variable_lengrh
의 binary OS label 을 저장할때 사용가능하다.
3.　indicators 없는 host 변수가 null을 fetch하면,　DBMS=V6으로
설정하지 않은 경우는
　　　ORA-1405를 return 함. PL/SQL table을 파라미터로 하는 stored
procedures 호출 가능.
4.　이전 version 에서 space 만 가능했던 (bug) input　character string
데이타 타입이
　　　terminator를 포함하는 경우도 이를 데이타로 인식 가능
(3)　version 1.6
==================
1.변경된 precompile option 으로　AUTO_CONNECT=YES option
지원하는데
이를 지정시는 처음 sql 문 수행시 OPS$<username>으로 자동 connect 된다.　
또한 CONFIG=<file> option 지원으로 user 의 configuration 의 name 과
위치를 지정할수 있다. 또한 시스템 config file 사용 가능한데 이의 위치는
UNIX = $ORACLE_HOME/proc16/pccc.cfg, VMS=ora_pcc:pccc.cfg. 이다.
2.　SQLSTATE 변수는 SQL문 실행 이후에 값이 설정된다. MODE=ANSI로 설정이
되어 있고, declare section안에 선언되어 있는 경우에만 이값이 설정된다.　
만일 그렇지 않으면 이 값은 무시된다.만약 SQLCODE가 안에 선언되어 있다면,
이 두 변수 모두 값이 설정된다.
　만약 SQLCODE가 밖에 선언되어 있다면 SQLSTATE만 설정된다. SQLSTATE는
coding scheme를 표준화하는데 사용된다. SQLCODE는　declare section
내부에 선언되거나, SQLSTATE, SQLCA가 사용되지 않는 경우에 사용하게 된다.
이 점은 1.5 버젼에서 SQLCA를 declare section 밖에 선언하여,　SQLCA와
같이 사용되었던 것과는 차이가 있다.
3.　SQLGLS 함수 지원하는데 이는 마지막 문장을 parse 한 후, 문장의 길이
및 타입을 return한다.　
eg)　int sqlgls(char *sqlstm ,size_t
*stmlen,size_t *sqlfc)
4.　select 문에서 stored function 을 call 할수 있다.
5.　단 SQLCHECK=FULL/SEMANTICS 가 아닌 경우에 FROM 절에서 subquery 가
가능하다. 이는 PL/SQL 의 semantic check 인 경우는 v7.3 에서 가능하다 .
(4) Version 1.8
================　
1.　INDICATOR VARIABLE을 사용하지 않고도 NULL FETCH시 ORA-1405 에러가
발생하지 않도록 UNSAFE_NULL=YES 옵션이 추가됨. UNSAFE_NULL=YES로
설정하면　ORA-1405 를 방지하기 위해서 DBMS=V6 으로 세팅할 필요없이
DBMS=V7 으로 할 수 있음. 단, UNSAFE_NULL=YES를 사용하기 위해서는
MODE=ORACLE 로 설정해야 함.
2.　PACKAGE ARGUMENT로 PL/SQL CURSOR(WEAKLY TYPED)를 사용할 수 있는데
예를 들면　TYPE GeneralCurTyp IS REF CURSOR;
3.　FROM 절에서 SUBQUERY를 사용할 수 있고 SQLCHECK=SEMANTICS 또는
SQLCHECK=FULL 옵션을 사용할 수 있음.
4.　PL/SQL 블럭에서 PL/SQL TABLE과 이와 관련된 다음 함수를 지원.
　a_table(index).EXISTS, a_table.COUNT, a_table.FIRST, a_table.LAST,
a_table.PRIOR(index), a_table.NEXT(index),
a_table.DELETE(start_index,_index), a_table.DELETE.
5. WHERE CURRENT OF CURSOR를 이용해서 MULTI-TABLE VIEW를 통해
KEY-PRESERVED TABLE을 UPDATE　가능.
(5)　version 2.0
==================
RDBMS version　7.3에서 부터　makefile 은
ins_precomp.mk,env_precomp.mk, proc.mk의 3 개로 나뉘었다.
Ins_precomp.mk 는 기존의 proc.mk 처럼 precompiler executables 를 build
하기 위한 routine 이고 env_precomp.mk 는 모든 environment 의 변수와
libraray 를 포함한다.
이 file 은 Ins_precomp.mk 와 proc.mk 에 포함되어 사용되어진다.
1.　V1.6과 같이 AUTO_CONNECT, CONFIG 옵션 지원. SYSTEM CONFIGURATION
FILE은 UNIX에서는 $ORACLE_HOME/proc/pmscfg.h 이고 VMS에서는
ora_proc20:pmscfg.cfg
2.　V1.6과 같이 SQLSTATE 변수와 SQLGLS 함수가 제공된다.
3.　C PREPROCESSOR가 포함되어서 #define이 EMBEDDED SQL과 함께 이용될 수
있고 #include 로 PRO*C 헤더화일을 INCLUDE 가능.
4.　구조체를 HOST 변수로 사용 가능.　이것은 SELECT INTO, FETCH INTO　
또는 INSERT시 VALUES 절에 사용될 수 있으나 PL/SQL PROCEDURE에 PL/SQL
RECORD ARGUMENT로 사용할 수는 없음.　구조체 내에 또다른 구조체를 포함할
수는 없지만　ARRAY는 포함할 수 있음.
5.　HOST 변수를 BEGIN/END DECLARE SECTION 안에 넣을 필요가 없음.
6.　V1.6에서 처럼 SELECT LIST에 STORED FUNCTION의 사용이 가능.
7.　SQLCHECK=FULL/SEMANTOCS를 사용하지 않는 경우 FROM 절에 SUBQUERY를
쓸 수 있음.
8.　CHARACTER 변수의 BIND TYPE은 MODE 옵션이 아니라 DBMS 옵션에 따라서
결정됨.　DBMS=V6/V6_CHAR 인 경우, CHARACTER는 TYPE 1, DBMS=V7(또는
NATIVE이고 ORACLE7에 접속할 때) 에서는 TYPE 97.
9.　DBMS=V6_CHAR 는 CHARACTER 변수가 가변 길이 문자열로 다루어질 수
있도록 함.
10.　SQLVCP 함수는 VARCHAR ARR 변수를 지정한 길이로 만들어 주므로
VARCHAR를 동적으로 할당할 때 COMPILER가 BYTE ALIGNMENT를 가능하게 함.
11.　PRO*C의 PARSE LEVEL을 설정하는 PARSE 옵션.
a)　NONE - PRO*C V1과 같음(HOST 변수를 DECLARE SECTION에 넣어야 함.
#define 인식 안함 등)
b)　PARTIAL - HOST 변수를 DECLARE SECTION에 넣어야 함
c)　FULL - PRO*C V2의 기능 모두 지원
12.　EXEC SQL WHENEVER ... DO 함수명(args,...); 와 같이 함수호출시UMENT를
주고 받을 수 있음.
13.　#ifdef/#ifndef 와 EXEC ORACLE IFDEF/IFNDEF 에서 사용하기 위한
DEFINE 옵션 지원.
(6) version 2.1
================
1.　PRO*C V1.7에서와 같이 char와 IMPLICIT VARCHAR (VARCHAR=YES 옵션과
함께 적절한 C 구조체로 선언된 변수) HOST 변수에서 MULTI-BYTE NLS
CHARACTER 데이타와 MULTI-BYTE 문자열을 지원.
　NLS_CHAR=var1,var2,... 옵션으로 MULTI-BYTE HOST 변수를 지정함.
MULTI-BYTE 리터럴은 다음과 같이 사용된다.
　EXEC SQL SELECT ... WHERE ENAME = N*이경구*;
　단, 이것은 SQLLIB RUNTIME LIBRARY를 통해서 지원되기 때문에 MULTI-BYTE
NLS 문자열은 DYNAMIC SQL에서 사용될 수 없음. NCHAR 데이타타입은 DDL 과
함께 사용될 수 없음.
2.　PRO*C V1.7과 같이 NLS_LOCAL 옵션 지원
3.　DEF_SQLCODE=YES 로 설정하면 PRO*C는 다음 문장을 생성한다.
　#define SQLCODE sqlca.sqlcode
　SQLCA는 반드시 INCLUDE 되어야 하며 SQLCODE 변수는 선언되어서는 안됨.
4.　PRO*C V1.7 과 같이 CURSOR VARIABLE 지원.
5.　VARCHAR=YES 로 설정하면 특정한 구조체를 VARCHAR로 인식할 수 있다.　
구조체의 형태를 보면
　struct
　short len;
　char arr[n];
　} host_var;
6.　CODE=CPP 로 설정하면 SQLLIB 함수 원형(PROTOTYPE)은 다음과 같이
extern "C" 형식으로 생성됨.
　extern "C" {
　void sqlora( unsigned long *, void *);
　그리고 "//" 와 같은 COMMENT 처리명령을 인식함. 단, CODE=CPP인 경우
PARSE 는 자동적으로 PARTIAL로 설정됨.
　CPP_SUFFIX 옵션은 PRECOMPILE된 화일의 확장자를 지정.
SYS_INCLUDE=(dir1,dir2,...) 옵션은 C 헤더 화일과 다른 위치에 있는 C++
헤더 화일이 있는 디렉토리를 지정. 이 옵션은 PARSE 옵션이 NONE이 아닌
경우에만 필요하다. HEADER 화일을 찾는 위치는 SYS_INCLUDE, 현재 디렉토리,
표준 SYSTEM 디렉토리(UNIX에서 PRO*C 헤더 화일의 위치는
$ORACLE_HOME/sqllib/public), 그리고 INCLUDE 옵션에 지정된 디렉토리이다.

Is a 11g cluster (11.1.0.7 ) can be use with 10g RDBMS (10.2.0.4)?

Hi,
We would like to upgrade to version 11g our 10g cluster (servers).
We would like to keep the rdbms to 10.2.0.4 for a couple of weeks, the time to be shure all the application do not have impact with the new RDBMS version (optimisation and performance).
In one single word, is it possible and secure to upgrade our cluster in 2 step?
1e step upgrade the cluster
2e step upgrade the rdbms (few weeks later)
I know i should upgade de two componants but is it possible and what can be the impact ?
I forgot to say the cluster is a 64-bit version
Edited by: ron_berube on 2009-09-14 13:44
Edited by: ron_berube on 2009-09-14 13:45

check metalink id: 363254.1
Applying one-off Oracle Clusterware patches in a mixed version home environment
and this:337737.1
Oracle Clusterware - ASM - Database Version Compatibility
so versions should always be like: crs =>asm>=rdbms
hth

Which OracleLite version to use?

I wish to install OracleLite but am unsure which version, 8i or 9i, will work with an old oracle database (RDBMS Version 7.3.4.5.0. )
Thanks

Oracle7 is no longer supported with Oracle Lite. You need at least 8.1.7.

Find the ORACLE Binaries version from OS

Hi,
I want to know the Oracle binaries version/release from OS itself.
Background : I am preparing the steps for upgrading my customer database. After upgrade of oracle binaries, i need to check the database release from OS for confirmation. But i am not able to find the command for this requirement.
Please help me.
Thanks

sorry, no luck
$ strings `which oracle` | grep -i version | grep oracle
Java_oracle_xdb_servlet_XDBCookie_get_1version
Starting up ORACLE RDBMS Version: %.*s.
oracletrace_facility_version
Target ID version %d
cluster interconnect IPC library is incompatible with this version of Oracle
Oracle interface version information %d.%d
* For Oracle versions 9iR2 and 10gR1, a transformation is performed
captured. For Oracle versions after 10gR1, if this is determined
:

I don't know which version of Oracle9i to download for XP Home Edition

I'm preparing for exam 1ZO-007 (Intro to Oracle9i SQL) and do not know which version of Oracle9i to download for XP Home Edition. Can somebody help? Thanks.

Hi,
unfortunately, NO oracle rdbms version is supported under XP Home, you need XP Professional.
Best regards
Wrner

RDBMS version

Similar Messages

Maybe you are looking for