Oracle - Apache PL/SQL Gateway Module - mod_owa - access remote server - apache

I have an Ubuntu 13.10 VM that I've created using Vagrant. This is meant to be a local development environment for a remote application using Oracle 11g and Oracle Fusion Middleware 11g.
What I want to do is, clone the application's code repository into the local VM and "route" the requests that are made on the local VM through the server where the application is hosted (DEV), so I won't need to install the database on the local VM together with all it's packages and procedures and also Oracle Middleware.
I came across Apache PL/SQL Gateway Module (https://oss.oracle.com/projects/mod_owa/dist/documentation/modowa.htm) which it's a substitute for Oracle Middleware.
I've installed and configured mod_owa on the VM, but when I restarted Apache I got the following error:
apache2: Syntax error on line 234 of /etc/apache2/apache2.conf:
Syntax error on line 1 of /etc/apache2/conf.d/mod_owa.conf:
Cannot load /usr/lib/apache2/modules/mod_owa.so into server: libclntsh.so.11.1:
cannot open shared object file: No such file or directory
Action 'configtest' failed.
The Apache error log may have more information.
...fail!
The above error makes me think that I still need to install Oracle 11g on the VM. Is there a way to bypass that error and make use of the remote server (DEV)?

I'm late to the party, but yes you need Oracle client installed on your apache server.

You need instant client with OCI (Basic): http://www.oracle.com/technetwork/database/features/instant-client/index-100365.html
Then to simplify your running environment:
As root:
Create a file oracle.conf under /etc/ld.so.conf.d
Single line in that file with a reference you oracle lib directory (oracle client home/lib)
run ldconfig
And you should be good to go.

Related

SQL Server service can not execute in centos

I want to install SQL Server on centOs.
I initial this service by command
sudo /opt/mssql/bin/mssql-conf setup
When I get status of service, I get this error:
Failed to start Microsoft SQL Server Database Engine
/var/opt/mssql/log/
I checked this location to see errors from SQL Server, but this location is empty.
Can you help me?
Larnu, Thank you For Answer
Answer:
SQL Server isn't supported on CentOS; I recommend using a supported
operating system.
I tried hard to solve this problem but I did not find a way and I decided to change my os

Error while connecting to Oracle Endpoint in Qlik replicate "cannot load libclntsh.so.11.1"

The replicate server is installed on Linux and i am trying to connect to a oracle database as source which is on a different server. While testing the connection i am getting the attached error message. The libclntsh.so is already defined in the oracle server machine. Kindly let me know the root cause of this.
You need to install the oracle client (you can download the rpm from technet) on the attunity replicate server and set the environment variable LD_LIBRARY_PATH.

Connecting sql developer to oracle 11g from lubuntu to centos

I have Installed sql-developer on Lubuntu and I want to connect sql-developer to oracle 11g, oracle 11g installed in another system(Centos)and sql-developer installed(Lubuntu) while testing the connectivity from sql-developer via tns service name its showing error as "Status -Test Failed: IO Error The Network Adapter Couldn't establish the connection". TNSPING is working for service names and ping ip-address is also working in destination sever where we have installed oracle 11g database.
Please let me know to resolve this issue.
Thanks,
Ranjithkumar
Could you please provide your TNS-Names File or the configuration of your SQL-Developer? The Error seems to occur because of a false Host-Definition. Be sure that you put in the right SID or Service name.
If you assume that your configuration must be right, please Check your DNS- and firewall-Settings. Further you can change into the Oracle-Bin Folder and execute the "tnsping" binary with the Host as Parameter.

IntelliJ and Local Tomcat: Mandatory?

Is it mandatory to have a local Tomcat Server in order to configure an Application Server in IntelliJ IDEA? My ultimate goal is to deploy to my remote Tomcat instance ONLY, without any local configurations.
Many thanks!
Tomcat Application server is used as a Provided dependency to get code completion and compilation of your code that utilizes JSPs and Servlets.
Remote debug configuration needs Tomcat Application server to know the target server version and uses local server libraries to perform connection and deployment.
So, yes, it's mandatory to have a local copy installed to use Tomcat Remote debug configuration.
If you are going to debug only plain Java code without JPS, use the plain Remote debug configuration like for normal applications, it doesn't require local application server installation.

SSIS & Business Objects SDK Error: File Repository Server Input is Down

Has anyone accomplished pushing files to a BOE server using SSIS? I am trying to develop a SQL Server 2008 SSIS package that will push report (Excel) files to our Business Objects Enterprise (BO XI 3.1) server. Via a Script Task, I am using the Business Objects .NET SDK components to authenticate and connect to the BOE Server.
I have a copy of the package deployed to a local instance of SQL Server 2008 running on my Windows XP desktop. The package executes successfully (via a SQL Agent Job) and delivers the file to the designated location on the BOE server.
When I deploy the package to our development SQL server (SQL Server 2008 on Windows Server 2008 64-bit) and attempt to execute the package via a SQL Agent job, I receive the error message "File Repository Server Input is down" when the script task attempts to "Commit" the file to the BOE server. The package is able to open a session with the BOE Server, create a new info object, but fails on the infoStore.Commit command.
I have another SSIS package that executes successfully from our development SQL server - it communicates with the BOE server and searches for user sessions. It does not communicate with the Input File Repository - that seems to be the key distinction.
I have found limited information related to this error that indicates firewalls and ports between the SQL Server and BOE server may be the cause. I have reviewed the BOE Administrator's Guide to no avail (most likely due to my lack of understanding related to firewalls and ports). Both servers are within the same subnet and neither server has the firewall turned on. The ports for the BOE CMS servers and the Input/Output File Repository servers have been set to static port ids. Our network guy indicates there should be nothing preventing communication between the servers based on firewall or port settings.
Any help would be greatly appreciated!
Have you tried all the usual 'run as 32 bit' solutions? I guess yuor SDK is a 32 bit one, not a 64 bit one.
http://www.bidn.com/blogs/ShawnHarrison/ssis/2362/ssis-basics-running-a-package-in-32-bit-mode
However the fact the the SDK works for different services implies that it runs OK in 64 bit. So if you want to troubleshoot ports, I found this link http://scn.sap.com/thread/2027785 which indicates that the BOE ports are 6400 to 6411. To check that a given port is open, you go to a DOS prompt and type
TELNET hostname port
So if your BOE server is BOESERVER then you'd try this:
TELNET BOESERVER 6400
to test port 6400. You should get a black screen to indicate it's connected.
However, again, the fact that you seem to be able to connect and operate but not commit implies there is not a port problem as you can connect, just can't commit.
Are there any logs in the BOE side to give you a better idea of the issue?
A resolution to this issue has been identified and verified. The Windows AD account used by the proxy the SQL Agent job uses to execute the SSIS package did not have sufficient privileges on the network. Our DBA gave the account local Windows administrator privileges on the SQL server and this resolved the "File Repository Server Input is down" error I was receiving.
Thanks to those who responded and gave me other ideas to investigate.