Unable to import application

[TheDarkKnight]

Hi ppl,
am facing issue in im;porting an application.

Following error appears when i try
-------------------------------------------------------------------
Unable to import application 'applcation name '

Caused by: org.jawin.COMException: 80010108: Unable to open connection. 0 .

Method '   ' of object '   ' failed[src=<SupplementalInfo><Source>OO4OHelper_85</Source><StackInfo><ErrorGuid>{FBE145CE-8E4C-4317-9C5A-A131BB33019E}</ErrorGuid><StackPosition>5</StackPosition><PreviousUserDomain> </PreviousUserDomain><PreviousUserName>cog1</PreviousUserName><PreviousComputerDomain></PreviousComputerDomain><PreviousComputerName> </PreviousComputerName></StackInfo></SupplementalInfo>,guid={AA000000-0000-0000-0000-0000000000AA}]
   at org.jawin.marshal.GenericStub.dispatchInvoke0(Native Method)
   at org.jawin.marshal.GenericStub.dispatchInvoke(GenericStub.java:201)
   at org.jawin.DispatchPtr.invokeN(DispatchPtr.java:587)
   at org.jawin.DispatchPtr.invokeN(DispatchPtr.java:555)
   at com.cognos.ep.appcontaineradmin.DataStoreCreator.ReConfigureImportTablesUsingSerializedProviderOptions(line 177)
   at com.cognos.ep.planningnetworktransfer.Import.importApplication(line 1569)
   at com.cognos.ep.planningnetworktransfer.Import.importApplications(line 414)
   at com.cognos.ep.planningnetworktransfer.Import.process(line 154)
   at com.cognos.ep.planningnetworktransfer.RequestProcessor.processRequest(line 77)
   at com.cognos.ep.planningnetworktransfer.Main.main(line 125)

See the log file for further details.

Please advice!

Cheers
TDK

[ericlfg]

Hi TDK,

1. Are you able to import any other deployment packages from the other environment? 
2. Conversely, are you able to export from this environment you're trying to import into?
3. At what point in the import does this error occur?  There should be a number of steps leading up to this failure.  A screen shot of this attached to this thread would help tremendously.

An initial thought is that it's trying to open a DB connection and is unable to.  This is the reason for my #3 question.  I'd like to confirm if the deployment import was able to create and start to populate the application container.

Cheers

[TheDarkKnight]

Hi eric,
Thx fr the reply,

1. Nope..not able to import any app from anyother env
2. Yes ..am able to export
3. Attached the snapshot fy ref. Its starts populating..but fails in the middle.

Thx.
TDK

[ericlfg]

So to confirm from the screen shot:

1. The application you're attempting to import via the deployment already has a datastore present.  So, you're overwriting an existing application? (common practice when migrating from one environment to another).

2. Have you attempted to use a different datastore name?  As a test, please try importing the package and on the final screen, click the 3 dots to the right of the application and then select your parent Datastore on the left in the new dialog.  This will allow you to modify the app display name, datastore name, and ID.  Try giving the 3 fields the name: test_import_DELETE. 

This will at least help us understand if you can in fact import into the environment, but just not over write the application DB containers.

[TheDarkKnight]

Eric,
Found out issue partially..

Presently able to import from other environment to this, but only able to overwrite an existing application.
earlier, the source and target datatore display names were different and i missed noting them down. with same application ids, datastore display name, i could able to overwrite existing app from other env also.

Now, when i try to create a new application, it was not wrking.[attached the error]. Also occurs when i try ot import an application with new datastore name, id and display name.

Iam not sure whether my steps are right, as still these are my initlal days in planning ???

[SomeClown]

It's likely database permissions.  Most Oracle DBMS implementations do not permit CREATE SCHEMA permissions to the account, and many times not even DDL permissions.  You'll probably need to turn on scripting to create new sql scripts for the DBA to run to create new applications.

[ericlfg]

While I agree with SomeClown to a certain extent, I would expect to see "ORA-01031: insufficient privileges" or some other extremely large error during the application creation wizard if there was a problem with permissions.

Some additional questions:
1. Are you guys using a clustered Oracle environment?
2. Do you know how the applications that are present in the target environment were created?  (newly created in this environment or deployment import?)
3. Have you been able to import deployments into this environment in the past?

[TheDarkKnight]

i tested the same datastore with different env of planning. With same access permissions, i could able to create Schema as well as new applications.

But not in the env iam facing issues.

[ericlfg]

Perhaps it's the Oracle client tools..  something missing, or an incompatible version.

Compare the Oracle client tools on the newest environment you just tested and were successful in with the original environment you're having problems with.

[TheDarkKnight]

HI Eric,
u got it right.
i finally got it resolved..its with oracle client version.
have two env's...Cognos planning server with Windows 2008 server, works only for oracle client 10.2.4 . it was not able to work with oracle cient 10.2.2 and orcale client 10.2.3 in my end.

Not sure, if this is an incompatibility existing with cognos in Windows 2008 env. If you know just letme know.
if u have any link pointing to the compatibility details.

Thx a ton!

Cheers
TDK

[ericlfg]

Hey TDK,

Glad to hear you got it sorted out and that it was something relatively simple.

As for the supported environments, I took a look up through the case and didn't happen to notice the version of planning that you're using.  I would expect though that you are on at least version 8.4+

You may find the supported environments page here:
https://www-304.ibm.com/support/docview.wss?rs=3449&uid=swg27014436&wv=1

Select your version and scroll down until you get to Planning Database Support.  This will outline what is compatible (previously tested in an older planning version) and what is actively supported (tested in this exact version).  If the version number is not listed, then it's not officially supported.  There are some grey areas here as most vendors will proclaim forward moving functionality, but it's not always the case.

Cheers!