Oracle 9i, OCI, and GCC on SPARC

does anyone have any successful experience compiling 9i oci apps on solaris using gcc? i've tried a couple of the demos with no success. i include the $ORACLE_HOME/rdbms/demo/demo_rdbms.mk files and altered a couple of variables (CCFLAGS, NOKPIC...) and got it to compile but segfaults on olog().
thanks.

Thank you for your reply.
I run the query:
select * from nls_database_parameters
where parameter in('NLS_LANGUAGE','NLS_TERRITORY','NLS_CHARACTERSET');
And he returned:
PARAMETER     VALUE
NLS_LANGUAGE     AMERICAN
NLS_TERRITORY     AMERICA
NLS_CHARACTERSET     CL8MSWIN1251
Then I set the variable NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252; export NLS_LANG
and tried to run ./frmcmp /oracle/formsp/CORE/FORM_NAME.FMB userid=XXX/XXX@XXX compile_all=yes batch=yes window_state=minimize
but received FRM-91500: Unable to start/complete the build.
Strange, but when you try to change the environment variable NLS_LANG, frmcmp can not run. If I do unset NLS_LANG frmcmp working properly.
Maybe it's something to do with the configuration of locale and fonts in Solaris?
Because I can not enter Russian or in graphical mode (when working through vnc) or in konsole mode (when connecting via putty) ...
It is worth mentioning that when I run the form, then all the data from the database appear in the fields correctly, in Russian. Incorrectly displays only those characters that belong to the form (such as titles of forms, labels on buttons, etc.).
Please help me find a solution.
Edited by: Tarasov_ES on 23.12.2009 19:45
Edited by: Tarasov_ES on 23.12.2009 19:50

Similar Messages

ORA-12504 error when connecting to Oracle 11G DB using OCI and instantclient-basic-nt-11.2.0.3.0.zip

Dear Friends,
I am using OCI and instant_client (11.2.0.3.0) in my C++ program (on Windows 7) to connect remotely to 11G database.
While doing a connection using server name as well as servername:port/service_name as connection strings, I am getting error of ORA-12504 TNS:listener was not given the SERVICE_NAME in CONNECT_DATA.
According to instant client FAQ & white paper at http://www.oracle.com/technetwork/database/features/instant-client/index.html, no tnsnames.ora is required for instant client. Then why could I be getting this error?
I ensured that only the instant client directory is in Path environment variable. There was a ODBC driver installed on this same host. Could that be modifying the behavior of instant client?
Kindly guide.
Many thanks in advance for your help and time.
Best Regards,
- ganesh

>>what is the exact connect string you are using?
For connection, I am using the plain hostname on which the DB server is running.
>>are you calling OCIServerAttach before OCISessionBegin?
I am not using OCISessionBegin. For connecting to DB server, I am using the following sequence of OCI calls (in this same order):
1) g_OCIEnvNlsCreate
2) g_OCIHandleAlloc //-- error handle: OCI_HTYPE_ERROR
3) g_OCIHandleAlloc // --- sevice context: OCI_HTYPE_SVCCTX
4) Setting driver name and application name for the session:
 OCISession* usersession = 0;
 ret = g_OCIAttrGet(m_pSvcCtx, OCI_HTYPE_SVCCTX, &usersession, NULL,
 OCI_ATTR_SESSION, m_pErrHdl);
 if (ret == OCI_SUCCESS)
 ret = g_OCIAttrSet(usersession, OCI_HTYPE_SESSION, (void*)"OCI_DRV", 2,OCI_ATTR_DRIVER_NAME, m_pErrHdl);
 ret = g_OCIAttrSet(usersession, OCI_HTYPE_SESSION, (void*)"ClientApplication", <ub4>(strlen("DataReconScanning")), OCI_ATTR_CLIENT_IDENTIFIER, m_pErrHdl);
5) g_OCILogon() using the user, password and host name, as below:
g_OCILogon(m_pDbCon, m_pErrHdl, &m_pSvcCtx,
 (text*)user.c_str(), static_cast<ub4>(user.length()),
 (text*)pass.c_str(), static_cast<ub4>(pass.length()),
 (text*)host.c_str(), static_cast<ub4>(host.length()));
Thanks.

What is the diffrence between OCI and OCCI?

What is the diffrence between OCI and OCCI?

Will Lee wrote:
What is the diffrence between OCI and OCCI?Beside the other answers, there are a few additional points to consider:
1) OCI is the "gold" standard API. New stuff is always available in OCI first, and only later trickles down to other APIs, like OCCI.
2) OCI is a low-level API, harder to get started with, than OCCI. APIs in OCI are often "untyped", taking a void*, which opens the door for errors.
3) In OCCI you set values, while in OCI you bind them. So OCCI takes a copy of your values, while OCI takes an address at which to later read the value. This opens the door to subtle bugs where you pass the address of a temporary in OCI, which later crashes in some mysterious ways. So OCCI is way safer in this regard.
4) OCI is C code, which is very portable. Because OCCI is C++ code, and on Windows you can't easily mix and match libraries compiled with different versions of Visual C++ (VC6, 7, 8, 9), you have to wait for Oracle to make a new build with the latest MS compiler. Just see the number of questions on this OCI forum and the OCCI one.
5) OCI is used internally by Oracle to write many of their own tools, it's the lingua franca between the Core DB group and the other groups. Since they use it themselves, it's much more stable that OCCI, which is mostly only used by outside customers.
6) The way SQL objects are dealt with in OCI and OCCI is fundamentally different, to the point where you can't mix and match OCCI and OCI object calls.
#1 above is one reason we had to abandon using OCCI, lacked support for the new in 11g BinaryXML, but that's just one example.
IMHO OCI is the way to go, if you want the latest and greatest. Yes, it's more difficult to code against, so the learning curve is steeper, but once you've reached critical mass it's just fine. If you write code in C++ as opposed to C, you can easily make it a lot safer with a thin C++ layer on top which, unlike OCCI, still allows you access any OCI raw handle to do stuff the wrappers don't expose. My $0.02 ;-) --DD

Oracle 8.1.6 on Solaris (SPARC) & EJB's

Hi all,
I would like to know if anybody is successfully using Oracle 8.1.6 on Solaris (SPARC) and EJB's or any other JServer Technology? If you have any advice for implementing JServer technologies on Solaris, please feel free to elaborate.
Thanks in advance,
Rob
null

Could you tell us how to do that????
We all met the ORA-01034 problem!
<BLOCKQUOTE>quote:<HR>Originally posted by Wile E. Coyote:
Yes, that's no problem
I've installed 8.1.6 on several machines running Solaris 8 without any problem<HR></BLOCKQUOTE>
null

Oracle 10g OCI based application talking to an Oracle 9i database

Hi all,
Got a question. I have an OCI C++ application that is written using the Oracle 10g OCI includes, etc ... This of course is running on a 10g client. The client OS is actually a Windows x64 system since 10g is the only native OCI client right now for 64 bit Windows systems. So this all works fine. Now, I am communicating with an Oracle 9i database server. Is there anything wrong or invalid about this configuration ? I didn't think that there was but I was asked to confirm this, that is having an Oracle 10g client communicating with an Oracle 9i database. Our application is making very straight forward OCI calls, and we are not using any of the newer OCI calls that were introduced in 10g, just the ones that are available in 9i OCI.
Thanks in advance,
Nick

Thanks for the reply.
Actually I thought that the OCCI forum was for Object oriented OCI, so while I'm using C++, I'm not using the object oriented side of OCI, just using the normal OCI calls. Guess I should have been a little clearer in my original post.
But my main question really concerned the version of the client and the version of the database which you answered.
Thanks,
Nick

Differences between Oracle JDBC Thin and Thick Drivers

If any body is looking for this information...
============================================================
I have a question concerning the Oracle JDBC thin vs. thick drivers
and how they might affect operations from an application perspective.
We're in a Solais 8/Oracle 8.1.7.2 environment. We have several
applications on several servers connecting to the Oracle database.
For redundancy, we're looking into setting up TAF (transparent
application failover). Currently, some of our apps use the Oracle
JDBC thin drivers to talk to the database, with a connection
string that like this:
 jdbc:oracle:thin:@host:port:ORACLE_SID 
In a disaster recovery mode, where we would switch the database
from one server to another, the host name in the above string
would become invalid. That means we have to shut down our application
servers and restart them with an updated string.
Using the Oracle OCI (thick) driver though, allows us to connect
to a Net8 service instead of a specific server:
 jdbc:oracle:oci8:@NET8_SERVICE_NAME 
Coupled with the FAILOVER=ON option configured in Net8, it is
then possible to direct a connection from the first server to
the failover database on another server. This is exactly what
we would like to do.
My question is, from an application perspective, how is the Oracle
thick driver different from the thin driver? If everything
else is "equal" (i.e. the thick driver is compatible with the
app servers) would there be something within the the thick/OCI
driver that could limit functionality vs. the thin driver?
My understand, which obviously is sketchy, is that the thick
driver is a superset of the thin driver. If this is the case,
and for example if all database connections were handled through
a configuration file with the above OCI connection string, then
theoretically the thick driver should work.
============================================================

In the case with the Oracle, they provide a thin driver that is a 100% Java driver for client-side use without the need of an Oracle installation (maybe that's why we need to input server name and port number of the database server). This is platform indipendent, and has good performance and some features.
The OCI driver on the other hand is not java, require Oracle installation, platform dependent, performance is faster, and has a complete list of all the features.

========================================================
I hope this is what you expect.
JDBC OCI client-side driver: This is a JDBC Type 2 driver that uses Java native methods to call entrypoints in an underlying C library. That C library, called OCI (Oracle Call Interface), interacts with an Oracle database. The JDBC OCI driver requires an Oracle (7.3.4 or above) client installation (including SQL*Net v2.3 or above) and all other dependent files. The use of native methods makes the JDBC OCI driver platform specific. Oracle supports Solaris, Windows, and many other platforms. This means that the Oracle JDBC OCI driver is not appropriate for Java applets, because it depends on a C library to be preinstalled.
JDBC Thin client-side driver: This is a JDBC Type 4 driver that uses Java to connect directly to Oracle. It emulates Oracle's SQL*Net Net8 and TTC adapters using its own TCP/IP based Java socket implementation. The JDBC Thin driver does not require Oracle client software to be installed, but does require the server to be configured with a TCP/IP listener. Because it is written entirely in Java, this driver is platform-independent. The JDBC Thin driver can be downloaded into any browser as part of a Java application. (Note that if running in a client browser, that browser must allow the applet to open a Java socket connection back to the server.
JDBC Thin server-side driver: This is another JDBC Type 4 driver that uses Java to connect directly to Oracle. This driver is used internally by the JServer within the Oracle server. This driver offers the same functionality as the client-side JDBC Thin driver (above), but runs inside an Oracle database and is used to access remote databases. Because it is written entirely in Java, this driver is platform-independent. There is no difference in your code between using the Thin driver from a client application or from inside a server.
======================================================
How does one connect with the JDBC Thin Driver?
The the JDBC thin driver provides the only way to access Oracle from the Web (applets). It is smaller and faster than the OCI drivers, and doesn't require a pre-installed version of the JDBC drivers.
import java.sql.*;
class dbAccess {
public static void main (String args []) throws SQLException
DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection
("jdbc:oracle:thin:@qit-uq-cbiw:1526:orcl", "scott", "tiger");
// @machineName:port:SID, userid, password
Statement stmt = conn.createStatement();
ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
while (rset.next())
System.out.println (rset.getString(1)); // Print col 1
stmt.close();
How does one connect with the JDBC OCI Driver?
One must have Net8 (SQL*Net) installed and working before attempting to use one of the OCI drivers.
import java.sql.*;
class dbAccess {
public static void main (String args []) throws SQLException
try {
Class.forName ("oracle.jdbc.driver.OracleDriver");
} catch (ClassNotFoundException e) {
e.printStackTrace();
Connection conn = DriverManager.getConnection
("jdbc:oracle:oci8:@qit-uq-cbiw_orcl", "scott", "tiger");
// or oci7 @TNSNames_Entry, userid, password
Statement stmt = conn.createStatement();
ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
while (rset.next())
System.out.println (rset.getString(1)); // Print col 1
stmt.close();
=================================================================

Wow, not sure what your question was, but there sure was a lot of information there...
There really is only one case where failover occurs, and it would not normally be in a disaster recovery situation, where you define disaster recovery as the obliteration of your current server farm, network and concievably the operational support staff. This would require a rebuild of your server, network etc and isn't something done with software.
Fail over is normally used for high availablity that would take over in case of hardware server failure, or when your support staff wants to do maintenance on the primary server.
Using the thin and thick driver should have ZERO affect on a failover. Transparent failover will make the secondary server the same IP as the primary, therefore the hostname will still point to the appropriate server. If you are doing this wrong, then you will have to point all your applications to a new IP address. This should be something that you tell your management is UNACCEPTABLE in a fail-over situation, since it is almost sure to fail to fail-over.
You point out that you are providing the TNSNAME, rather than the HOSTNAME when using the thick driver. That's true within your application, but that name is resolved to either a HOSTNAME, or IP ADDRESS before it is sent to the appropriate Oracle server/instance. It is resolved using either a NAME server (same as DNS server but for Oracle), or by looking at a TNSNAMES file. Since the TNSNAMES files profilerate like rabbits within an organization you don't want a fail over that will make you find and switch all the entries, so you must come up with a fail over that does not require it.
So, the application should not be concerned with either the hostname, or the IP address changing during fail over. That makes use of the thin or thick client acceptable for fail over.
Don't know if this will help, but this shows the communication points.
THIN DRIVER
client --> dns --> server/port --> SID
THICK DRIVER
client --> names server --> dns --> server/port --> SID
client --> tnsnames --> dns --> server/port --> SID

Essbase 11.1.2.1 - Dimension build problem, OCI and SQL...

When retrieving SQL data in Data Prep editor, field names are replaced with SQL View field names.
From what I can find this was supposed to be fixed in the patch for 11.1.2, can anyone confirm or deny that...
Is this only a problem with OCI and ODBC connections?
Any help would be appreciated.
Adam,

We are experiencing all of the defects:
Defects Fixed in this Patch
· 13398150 – When you use the Migration Wizard in Administration Services to migrate an Essbase application, an incorrect error message is returned: "Failed to migrate the application. Please see message panel for details." However, the application is migrated. Refresh the Essbase server application node to see the migrated application.
· 13398160 – Selecting the OK/Retrieve button to populate data from SQL causes previously defined column headers to be changed.
· 13398169 - Joining two or more data fields in Data Prep Editor, when one or more of the fields is empty, causes Administration Server to terminate abnormally.
I think the patch would work if it weren't for the limited processors supported... were running Intel Zeons. How do we get ORACLE to compile patches for them... ???
Supported Platforms
· Microsoft Windows (32-bit) (console)
· Microsoft Windows x64 (64-bit) (server)
· Linux AMD (64-bit) (server)
Edited by: Adam M on May 18, 2012 2:52 PM

Oracle 9.2 and PHP 5.1.x problems

Hello everyone.
I have an extremely frustrating dilemma, which has been a pain for quite a while now.
I have been working with Oracle and PHP since Oracle 8.x and PHP4 and everything has been running smoothly. After we upgraded from PHP4 to PHP5 and from Oracle 8 to Oracle 9 I had to switch from using the old php_oracle extension to the OCI-libraries, but otherwise there were no problems.
But now I am completely stumped. We are currently using Oracle version 9.2 and since our production enviroment is extremely large we are not going to upgrade to Oracle 10 or greater for many years.
PHP though keeps on going forward. I am currently using PHP 5.1.0. I have tried several times upgrading to anything beyond that. 5.1.2, 5.1.4 and recently 5.1.6. But the oracle extensions just don't want to play anymore.
I get the following error message everytime I start my apache 1.3:
The procedure entry point OCILobRead2 could not be located in .. OCI.dll
After reading this thread
(Re: "The procedure entry point OCILobRead2 could not bel located in .. OCI.dll"
I seem to know what the cause of the problem is. But how can I get past this? I would really like to upgrade our PHP version and still be able to use oracle. 5.1.0 is the last version which seems to work ok. Anything greater than that will not work at the moment.
Any help would be greatly appreciated. Thank you very much.
EDIT: I am using Windows 2000 and Windows 2003 Server. Unfortunately Linux is not an option where I work.
EDIT2: Another edit. Actually I can start the thing up with PHP 5.1.2, but then I get a weird apache crash whenever I try to run a simple select query. No error messages and the log is empty. I am completely stumped.
Message was edited by:
Gameon
Message was edited by:
Gameon

Thanks for the answers. The oci8.dll is uncommented naturally. Otherwise it would start up just fine, but I couldn't use the database functions.
I got it working by installing 5.1.6, but replacing the oci8.dll with the one from the 5.1.0 -version. It's a very... desperate... solution, but at least it works.
I'm gonna have to try to sell the idea of using the 10g client to our DBA. I don't think though, that he'll be very enthusiastic to set it up on our production servers. We'll see.

Oracle SQL*Net and TNS Protocol

I need to get technical documents on Oracle SQL*Net and TNS Proticol, down to the bit-level definition. I have talked to serveral people in Oracle Documentation, Sales and Tech Support, but no one could give me any clue so far. Any one can help me on this?

SQL*Net is installed by default with SQL*Plus and any of the clients (OEM uses the JDBC OCI driver and some native connectivity).
It is likely that the version of the client you have installed is not one that TOAD can work with or it can't find the client (is the Oracle home/bin directory in the path?)

Oracle data source and Sun App Server 8

Hi -- This could be more of a JNDI question than a JDBC question... Please let me know if I have posted to the wrong place.
I downloaded Sun Application Server version 8 and installed it on a windows 2000 pc. The install went fine, as did the build and deploy of the jdbc-simple .ear file. I can run jdbc-simple with no problems.
Now, through the App Server Admin Interface, I have added a new connection pool utilizing Oracle's OCI driver and I can successfully ping the database from App Server. I created a JDBC Resource that uses the Oracle pool and gave it the JNDI Name "jdbc/oracle-dev ". At this point, I am stuck. I want to use "jdbc-simple" to connect to my new JDBC Resource instead of the pointbase resource.
Could someone please help me make the necessary modifications to jdbc-simple so that is uses the new "jdbc/oracle-dev " JDBC Resource I created rather than the pointbase connection that was supplied by default during install?
Thanks for any help,
Jason Earnhardt

That helpes quite a bit. I still can't get the app to retrieve data, but I am getting a more useful message in the log:
[Error in allocating a connection. Cause: Connection could not be allocated because: ORA-01017: invalid username/password; logon denied]
As you suggested, I removed the <default-resource-principal> stuff from sun-web.xml and modified it to match your example. Additionally, I changed the <res-ref-name> in web.xml from "jdbc/jdbc-simple" to "jdbc/oracle-dev".
The Connection Pool "Ping" from the Admin Console is successful with the user and password I have set in the parameters. (it fails if I change them, so I am pretty sure that is set up correctly) Is there another place I should check for user/pass information? Do I need to do anything to the samples/database.properties file?
By the way, this is the 4th quarter 2004 release of app server. Would it be beneficial to move to the Q1 2005 beta?
Many thanks for your help so far...

Choice of OCI and ODBC

anyone written C++ app using ODBC API on Solaris platform to access Oracle db?
I was told there are 3 party software ODBC driver. Anyone has experience in this area?
thanks in advance for your help and any opinion you have between the choice of OCI and ODBC (on a Solaris platform)
null

The biggest speed difference will be if you buy a SSD.
| X220 i7-2620M | 12.5" IPS | Intel 520 Series 180GB Main SSD | Mushkin 120GB mSATA SSD | 8GB RAM | Intel 6205 WiFi | BT | Win7 Pro 64 SP1 |

Toad Error - Cannot load OCI DLL: C:\Oracle\instantclient_11_1\oci.dll

Hello All,
Help needed to fix this error.
We are getting the below error from Toad after fresh install on Windows 7 64 Bit.
Toad for Oracle Base
Version: 10.6.1.3
Cannot load OCI DLL: C:\Oracle\instantclient_11_1\oci.dll
We are using the Oracle Instant Client (instantclient-basic-nt-11.2.0.2.0).
We are able to connect to the database from the command line successfully, but when we tried to launch the Toad and connect it we are getting the above error.
How do we fix this issue?
Thanks in advance.
Sandeep S

mseberg wrote:
So is this a Toad issue or an Oracle client issue?More like a general software or programming "issue". If Toad (or other program) is 32-bit, then loaded libraries (e.g. Oracle Client dll's) needs to be 32-bit.
I'm sure this is documented in requirements for Toad. See e.g. [url http://toadfororacle.com/servlet/KbServlet/download/4264-102-12585/10.6_ReleaseNotes.htm#SystemRequirements]Toad 10.6 Release notes.
Edited by: orafad on Aug 10, 2011 2:35 AM

How a procedure is compiled in oracle ? (implicit and explicit compilation)

how a procedure is compiled in oracle ? (implicit and explicit compilation)

When you create a proceudre oracle automatically compile and stored it. Use the following syntax to compile a procedure
ALTER PROCEDURE hr.remove_emp COMPILE;
Thanks

Not able to see ikm oracle incremental update and ikm oracle slowly changing dimensions under PHYSCIAL tab in odi 12c

not able to see ikm oracle incremental update and ikm oracle slowly changing dimensions under PHYSCIAL tab in odi 12c
But i'm able to see other IKM's please help me, how can i see them

Nope, It has not been altered.
COMPONENT NAME: LKM Oracle to Oracle (datapump)
COMPONENT VERSION: 11.1.2.3
AUTHOR: Oracle
COMPATIBILITY: ODI 11.1.2 and above
Description:
- Loading Knowledge Module
- Loads data from an Oracle Server to an Oracle Server using external tables in the datapump format.
- This module is recommended when developing interfaces between two Oracle servers when DBLINK is not an option.
- An External table definition is created on the source and target servers.
- When using this module on a journalized source table, the Journaling table is first updated to flag the records consumed and then cleaned from these records at the end of the interface.

Memory and No. of Processor calculation for Oracle EBS R11 and R12

Can some one please tell me …. How to calculate required Memory and No. of Processors for Oracle EBS R11 and R12.
For example we have 50 Concurrent users and 100 named (i.e. the users which are doing only Data entry.), so how to How to calculate required Memory and No. of Processors
Please guide me on the same.
Thanks,

Please refer to the following links, it may be helpful:
Oracle Applications Benchmark White Papers
http://www.oracle.com/apps_benchmark/html/white-papers-e-business.html
Oracle Applications Standard Benchmark White Papers
http://www.oracle.com/apps_benchmark/html/white-papers.html
Hardware requirements for Oracle APPS
Hardware requirements for Oracle APPS

Oracle 9i, OCI, and GCC on SPARC

Similar Messages

Maybe you are looking for