Work repository on different database configuration

Hello there,
I am trying to set my work repository to be a schema on differing database to the source dataserver.
Currently when I edit the source data server and try to set the work repository I only have the option to select schemas from the source.
I have my work repository on a different database.
Can anyone help?
Regards,
CM

I have come to a conclusion that there has been a confusion over the terminologies. What you call "Work Repository" is actually a "Work Schema" in your specific case.
Then the answer is that Work Schema needs to be on the same data server as your Source Schema.
Below is a reasoning behind that:
This schema consists of temporary/intermediate work tables that are generated by ODI knowledge modules.
These work tables are similar to tables in source schema in terms of data and structure
Data is moved, copied and compared between source schema and work schema, it makes more sense to store them on the same data server to avoid any network/communication overhead.
Hence ODI warrants that the source schema and the work schema exist on the same data server.
P.S. "Work Repository" is the metadata repository that holds the data model definitions, ODI code, packages, interfaces, etc.
It works in tandem with "Master Repository"
Hope this helps you.
If you feel that your question has been answered, please mark the question as answered and all the answers that you have received as helpful or correct.
Thanks

Similar Messages

Deployment to runtime repository in different database hangs

Hi All
I am facing an issue while deploying to a runtime repository in different database.
I have created a simple mapping,taking data from one schema available in database where OWB is installed, to schema available in different database.I am changing the configuration to the control center available on target database.
source module is associated with control center available on design repository and target module is associated with control center available on runtime repository.
In control center manager,the message displayed at toolbar is "compiling deployment object"..after sometime OWB hangs and nothing happens.
What could be possible reason for that?
Thanks in advance
Avanish

I got the problem with OWB 10.1.0.4.0 and I had to install the path 10.1.0.5.0 for make it works !

Master and work repository grouping

Hi , what is the most efficient and industry standard model of grouping master and work respository.
. is it good to group master and related work for every technology like DB2 , SQl server etc ?
or
is it good to group master and related work repository depending on the project where we can have different technologies grouped in single work repository and multiple work repository for different technologies. ?
Please share with me with your company standard or views on my above question.
Thanks
Dev

As far as I know it is not recommended solution to create both master and work repositories in one Oracle schema, better create them as separate schemas.

Mapping to different databases

We currently use TOPLink as persistence layer in our product. Currently the complete object model maps to one database. I was wondering if it is possible to map different objects to different physical databases (with different structures). E.g. We map the income object to a certain table in db1 (database only containing income data) and the investment portfolios to another database; etc.
Does anybody has experience with this? Thanks for your reply.

Hi,
In order for you to work with two different databases at the same application you will need to use Session Broker.
You can find an example of doing such a thing under "D:\toplink903\examples\core\examples\sessions\broker".
In addition, you can find a large section in the 'TopLink foundation library' about the subject.
Raanan.

Error while configuring work repository details in topology Manager

Hi,
Could anyone pls advice, is it possible creating more than one Master repository connection for the same instance.
When i try to do so, am getting the below error while configuring the work repository details in topology manager.
“A work repository already exists for this connection.
Enter the repository password to declare it in your Master Repository”
I tried with both the new master and work repository password. But no luck.
Previous Master & work details:
Master: PCS_MASTER
Work:PCS_WORKREP
New Details
Master: PCS_MASTER_INT
Work:PCS_WORKREP_INT
Instance: PCBID
Am trying to create new master repository for PCS_MASTER_INT.

In the same oracle schema you can have only 1 master and 1 work repository. Usually they take 2 schema (1 for each).
If you need 2 master repository you have to use 2 different jdbc path. I'm using a db with several master / work, each repo has got its schema..

Oracle 9.10 Database Configuration Assistant not working

I have installed Oracle 9i Enterprise Edition on Windows XP, Pentium 4 and everything installed successfully but after installation, when I click on Database Configuration Assistant, nothing happened, no error displayed, mouse flashed for a while as loading something then came normal. Any idea please ?
Even Database Migration Assistant also not working.
I also could not find svrmgr utility in Oracle 9i to create a new database.
Best Regards,
Luqman

The Server Manager was deprecated in 9i. Instead of using it you have to use the SQL*Plus. Do you have another JRE installed ?
How to create a database manually in 9i
Administrator's Guide for Windows Contents / Search / Index / PDF
http://download-east.oracle.com/docs/cd/B10501_01/win.920/a95491.pdf
Joel Pérez

How to schedule two jobs from two different work repository at a time?

Hi All,
I have a scenario where I want to schedule two jobs at a time from two work repository.
Explanation:
Master Repository-A
Work Rep-B
Work Rep-C
Now I need to schedule two scenario one from Work rep B and other from Work Rep-C
As we know that odiparams batch file contains the connection details and at one time it can hold only one work repository name.
Odiparams data:
rem Repository Connection Information
rem
set ODI_SECU_DRIVER=oracle.jdbc.driver.OracleDriver
set ODI_SECU_URL=jdbc:jdbc:oracle:thin:@10.10.10.10:1521:orcl
set ODI_SECU_USER=odi_snpm
set ODI_SECU_ENCODED_PASS=aYyHZZCrzk5SjQ9rPOIUHp
set ODI_SECU_WORK_REP=*ODI_LOCALDEV_WRKREP*
set ODI_USER=SUPERVISOR
set ODI_ENCODED_PASS=LELKIELGLJMDLKMGHEHJDBGBGFDGGH
Scheduler agent will pick this information from the odiparams file and update the schedule.
So If I want to schedule two job, how it is possible?
I tried all possible things but didn't get the proper solution?
Edited by: user10765509 on Jul 21, 2010 4:58 AM

You can do it in the following way
1. copy/paste the original odiparams.bat file
2. give it a name say odiparams_a.bat
3. specify the work repository A related information in odiparams_a.bat
4. Make another copy of odiparams.bat file
5. give it a name say odiparams_b.bat
6 specify the work repository B related information in odiparams_b.bat
7. now make 2 copies of agentscheduler.bat give the name as follows
agentscheduler_a.bat and agentscheduler_b.bat
8. edit agentscheduler_a.bat and change
call "%ODI_HOME%\bin\odiparams.bat"
with
call "%ODI_HOME%\bin\odiparams_a.bat"
9. edit agentscheduler_b.bat and change
call "%ODI_HOME%\bin\odiparams.bat"
with
call "%ODI_HOME%\bin\odiparams_b.bat"
10. now start two scheduler agent by calling agentscheduler_a.bat and agentscheduler_b.bat
Thanks,
Sutirtha
PS : Take a backup of each and every file getting modified

APEX Application accessing data from two different databases

Hi All,
Currently as we all know that APEX Application resides in database and is connected to the schema of that database.
I want APEX Application to be running and accessing data from two different databases. Elaborating my question,
Currently, my APEX Production Application is connected with XXXX Schema of DB1 Database(Where APEX Resides). Now I want to add some pages into this APEX Application for REPORT Purpose, But I want to connect this REPORT APEX Pages to get data from Different Schema YYYY for Database DB2.
Is it possible to configure this scenario?
The reason for doing this is to avoid the REPORT related (adhoc queries) resource utilization effect on Production DB1 Database.
Thanks
Nil

1. If you do the joining of two or more tables in DB1 then all data is pulled over to DB1 and then the join is executed: so more data over the databaselink and more work for DB1. Better keep the joining stuff where the data resides and just pull exactly that data over that you need.
2. Don't know about your different block sizes. Seems a nice question for one of the other forums (DBA or SQL).
3. I mean create synonyms on DB1 for reports VIEWS in DB2.
Hope all is clear!

JMS JDBC store failed to open after switched to a different database machine

          Hi,
          I'm running WebLogic 6.1 sp3/Oracle 8.1.6 and I configure the JMS JDBC store for
          persistent messaging. I was working fine until I switched to use a different database
          machine which has the same software configuration as the old one. It was giving
          me "failed to create tables" error at start up time. But I checked the database
          and found out the two tables (<prefix>JMSSTORE and <prefix>JMSSTATE) were both
          created and I was able to query although they don't contain any data. By the way,
          I'm using thin client.
          Anyone can help? Thanks a lot!
          Here's the exception:
          <Jul 23, 2003 4:33:10 PM PDT> <Alert> <JMS> <JMSServer "notifyServer", store failed
          to open, java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix
          = <qa.JMS_SERVER_>: failed to create tables.
          java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix = <qa.JMS_SERVER_>:
          failed to create tables
          at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:311)
          at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1400)
          at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:376)
          at weblogic.jms.store.JMSStore.open(JMSStore.java:110)
          at weblogic.jms.backend.BEStore.open(BEStore.java:180)
          at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
          at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
          at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
          at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy39.updateDeployments(Unknown Source)
          at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
          at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
          at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy58.start(Unknown Source)
          at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          at weblogic.management.Admin.finish(Admin.java:644)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          at weblogic.Server.main(Server.java:35)
          >
          <Jul 23, 2003 4:33:10 PM PDT> <Error> <JMS> <Failed to deploy JMS Server "notifyServer"
          due to weblogic.jms.common.ConfigurationException: JMS can not open store.
          weblogic.jms.common.ConfigurationException: JMS can not open store
          at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:395)
          at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
          at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
          at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy39.updateDeployments(Unknown Source)
          at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
          at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
          at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy58.start(Unknown Source)
          at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          at weblogic.management.Admin.finish(Admin.java:644)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          at weblogic.Server.main(Server.java:35)
          ----------- Linked Exception -----------
          java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix = <qa.JMS_SERVER_>:
          failed to create tables
          at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:311)
          at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1400)
          at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:376)
          at weblogic.jms.store.JMSStore.open(JMSStore.java:110)
          at weblogic.jms.backend.BEStore.open(BEStore.java:180)
          at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
          at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
          at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
          at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy39.updateDeployments(Unknown Source)
          at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
          at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
          at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy58.start(Unknown Source)
          at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          at weblogic.management.Admin.finish(Admin.java:644)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          at weblogic.Server.main(Server.java:35)
          >


Hi Michelle,
          I suspect a permission problem where the new tables are created
          using the JDBC driver's default schema, but the prefix
          specifies another schema "qa". So the tables are getting
          created, but aren't found.
          Work-around one:
          manually extract, edit, and run the ddl that creates
          the tables to specify the schema. Prepend
          "qa.JMS_SERVER_" to all table names
          (This is fairly simple to do.)
          http://edocs.bea.com/wls/docs61/jms/appb.html#999286
          Work-around two:
          Don't include "qa." in the prefix.
          (i'm not sure if this will work)
          Work-around three:
          Change the username of the JDBC pool to "qa".
          (i'm not sure if this will work)
          Work-around four:
          Change the schema for the tables that were created
          under the JDBC driver's default schema to "qa".
          (I'm not sure how this is done, or even
          if it is possible. Database specific.)
          Tom
          Michelle Lian wrote:
          > Hi,
          >
          > I'm running WebLogic 6.1 sp3/Oracle 8.1.6 and I configure the JMS JDBC store for
          > persistent messaging. I was working fine until I switched to use a different database
          > machine which has the same software configuration as the old one. It was giving
          > me "failed to create tables" error at start up time. But I checked the database
          > and found out the two tables (<prefix>JMSSTORE and <prefix>JMSSTATE) were both
          > created and I was able to query although they don't contain any data. By the way,
          > I'm using thin client.
          >
          > Anyone can help? Thanks a lot!
          >
          > Here's the exception:
          >
          > <Jul 23, 2003 4:33:10 PM PDT> <Alert> <JMS> <JMSServer "notifyServer", store failed
          > to open, java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix
          > = <qa.JMS_SERVER_>: failed to create tables.
          > java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix = <qa.JMS_SERVER_>:
          > failed to create tables
          > at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:311)
          > at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1400)
          > at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:376)
          > at weblogic.jms.store.JMSStore.open(JMSStore.java:110)
          > at weblogic.jms.backend.BEStore.open(BEStore.java:180)
          > at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
          > at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
          > at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
          > at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
          > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
          > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
          > at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
          > at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > at $Proxy39.updateDeployments(Unknown Source)
          > at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
          > at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
          > at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > at $Proxy58.start(Unknown Source)
          > at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
          > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          > at weblogic.management.Admin.finish(Admin.java:644)
          > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          > at weblogic.Server.main(Server.java:35)
          >
          > <Jul 23, 2003 4:33:10 PM PDT> <Error> <JMS> <Failed to deploy JMS Server "notifyServer"
          > due to weblogic.jms.common.ConfigurationException: JMS can not open store.
          > weblogic.jms.common.ConfigurationException: JMS can not open store
          > at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:395)
          > at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
          > at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
          > at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
          > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
          > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
          > at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
          > at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > at $Proxy39.updateDeployments(Unknown Source)
          > at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
          > at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
          > at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > at $Proxy58.start(Unknown Source)
          > at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
          > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          > at weblogic.management.Admin.finish(Admin.java:644)
          > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          > at weblogic.Server.main(Server.java:35)
          > ----------- Linked Exception -----------
          > java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix = <qa.JMS_SERVER_>:
          > failed to create tables
          > at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:311)
          > at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1400)
          > at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:376)
          > at weblogic.jms.store.JMSStore.open(JMSStore.java:110)
          > at weblogic.jms.backend.BEStore.open(BEStore.java:180)
          > at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
          > at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
          > at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
          > at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
          > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
          > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
          > at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
          > at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > at $Proxy39.updateDeployments(Unknown Source)
          > at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
          > at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
          > at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
          > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
          > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > at $Proxy58.start(Unknown Source)
          > at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
          > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          > at weblogic.management.Admin.finish(Admin.java:644)
          > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          > at weblogic.Server.main(Server.java:35)
          >

Crystal Report Server: Cannot save Database Configuration in CMC

I already posted this question as SAP internal CSN message (message number 1896093 2009) but did not get any answer so far.
I have installed a test version (which I'd like to become permanent some
day...) of Crystal Reports Server 2008 on a local machine to be able to
share Crystal reports within our department.
I created a couple of reports which I would like to get updated
regularly. The issue is here that I get a logon screen to the underlying
SQL Server as soon as a user clicks on "Refresh" when viewing a report
from InfoView. The SQL Server is running on integrated security
via SSO, which I cannot change...
To get around this issue I would like to change the default Database
Configuration of the reports. Hence I do the following:
1) I open the Central Mangement Console
2) I select one of my reports
3) Rightclick on Properties
4) On the Default tab I select Database Configuration
5) the config is set to "Logon Screen" and I ant to change this to SSO,
so I set this
6) Now I click on Save
=> The setting is reverted to the old "Logon Screen" settin1g
This behavior is the same for all the reports I'm using.
Looking forward to any help, kind regards
Wolfgang
P.S.: Ultimately this issue arises, because I cannot refresh my crystal report data in batch job mode, because the reports are reading data from an SQL server, which allows SSO-logon (integrated security) only. Thus I have to open each and every report for update manually and click on the refresh button.
Edited by: Ralf Wolfgang Geithner on Jul 3, 2009 11:00 AM

Hi Manish,
thanks for your answer. Unfortunately I'm still stuck in this matter.
Does this happen with the sample reports too? I think it will be a good approach to try this to see if your system is behaving differently for sample reports and reports published from outside
I did not really try this, but viewing and editing my reports in Crystal Reports 2008 Designer works perfectly fine. As well can the user view my reports in the InfoViewApp.
Also, does it revert to the login screen setting immediately after you click Save or does it show the setting as changed after clicking Save but, does not retain it when you come back and check the report settings again?
The data is reverted immediately after clicking "Save"
Kind reagrds
Wolfgang

Connecting to two different database instances from a swing application.

Hi All,
I am developing a swing application which needs to interact with two different database instances of two different weblogic servers.
More eloborately,
I have some data in DB_Instance1 running on[b] Weblogic_Server1 and I need to insert the same data into DB_instance2 running on Weblogic_server2. Is it possible. Could some explain me how to do that..
Thanks in advance...
Sreekanth.

Hi Rick,
Try logging onto both Server first. You'll have to use either 2 separate ODBC DSN's or 2 separate OLE DB connections. Set them both for Trusted Authentication, you'll have to configure that on the Server also.Then try your query.
If that doesn't work then you'll have to create a Stored Procedure or View that can link the 2 Server side.
Thank you
Don

Business Rule Repository has not been configured?

Hi,
In EAS trying to open Business Rules, I get "Repository has not been configured or you are not authorized to use Business Rules" (I get this with the admin creds)
In details, "Error loading objects from Data Source", "SQLSyntaxExceptionError: ORA-00942 table or view does not exist"
This is relatively new Production install running v. 11.1.2.1
I ran into this after my LCM migration of a Planning app failed, unable to create business rules.
IT folks tell me "the database looks fine" when I asked them about the ORA-00942 table.
Can anyone help point me to a configuration step that might have been missed?
Everything works in development environment, so if there's something to compare between the two, I'd appreciate any help.
Thanks,

Its necessary to do the following
SE80 -> BSP Application -> Tunguska -> Pages with Flow Logic -> start_sts.htm or start_sts2.htm-> Right click & display in same window -> Properties tab -> Transfer Options -> HTTPS should be UNCHECKED.

ODI-10150: Work repository with ID 1 is not bound to master

Hello,
ODI 11g (11.1.1) with database 11g r2
I have created Master repository (odimrep) and
work repository(odiwrep), created from Topology
Before the next step, during this time I was able to login to connect to work repository and able to do all work
Then I went on to created Execution repository (odierep) from topology, created successfully.
After that I could not able to connect to work repository, as I am getting the following error message
oracle.odi.core.config.RepositoriesNotBoundException: ODI-10150: Work repository with ID 1 is not bound to master:
Definition in master ID:1, Name:ODIWREP, Timestamp:1337006142714
Definition in work ID:2, Name:ODIEREP, Timestamp:1337006565503.
.....Could you please let me know what I am doing wrong to configure the Execution repository, do I need to drop everything and start re-create
Any help would be greatly appreciated.
Thanks,

Hi,
It should not really create any problem , if you create a two work repositories with differenct IDs. But, the error messae you gave suggests , it is something to do with repository IDs. Usually, we get this message , when we try to migrate ODI code within enviroments. However, it does not throw as an error message, it just gives as an information and asks us if we want to register the new work repository ID. We just need to say Yes and continue.
I would suggest to redo everything, recreate repositories again. May be something went wrong while creating repositories.
Regards,
k

Setting up different databases

I need some help in uderstanding how data bases are setup in Oracle.
Let me be more specific. In Access one can setup a different database and "save" it. One can then create tables within each of these "independent" databases.
Can one do the same with Oracle ? I seem to always be working with just one database [and all the tables in that database]. When I log into Oracle [8i] I don't seem to get a "choice" of databases the way I do in Access.
I would appreciate an explanation [or comments] on this.
Thanks
null

this is the section from new features list I had on mind:
Release Notes
1 New Features for Oracle Database Lite 10g Release 3
1.9 Store Application Data in Separate Databases
By default, all application data is stored in the same database as the Mobile repository. However, you can register other Oracle databases as the repository of the application data. Once registered, then during the publication creation, specify the database where you want the application data to be stored.
This feature should allow you to use two (and even more) different database schemes for your sync snapshots if I understand it right. I didn't test it yet to verify it unfortunately. So if you'd test this new feature than let us know, please..

ODI Demo Environment - Work Repository issue

I'm a newbie to ODI, and have downloaded the software and the demo environment (plus instructions). Setup seems to go fine, but when I get to the point where I should connect to the demo environment, I follow the instructions but am unable to type in WORKREP as the Working Repository - the field is greyed out, and I cannot proceed further.
I have started the demo environment using startdemo.bat, and everything else seems OK (or at least doesn't error) aside from this.
Am I correct in saying that the RCU does not need to be run, just to use the Demo Environment?
Please can anyone help? I would like to evaluate the product but have run up against this wall.
Many thanks,
Ian

Hi,
I had similar issue on Windows..
Solution,
1) I downloaded jrockit SDK.
2) Pointed JAVA_HOME to this installation
3) Extract the demo folder (i.e. under <ODI_HOME> as odidemo)
Start the agent.
Run ODI enter the details as described in http://download.oracle.com/docs/cd/E14571_01/integrate.1111/e12641/start_odi.htm.
Specify the Oracle Data Integrator connection details as follows:
Login name: Getting Started - ETL Project
User: SUPERVISOR
Password: SUNOPSIS
Note that username and password are case sensitive.
Specify the Database Connection (Master Repository) details as follows:
User: sa
This is the database user ID/login of the schema (database, library) that contains the ODI master repository
Password: Leave this field empty.
Driver List: Select Hypersonic SQL Driver from the list.
This driver is required to connect to the DBMS supporting the master repository.
Driver Name: org.hsqldb.jdbcDriver [This is different when populated by ODI]
URL: jdbc:hsqldb:hsql://localhost
or
jdbc:hsqldb:hsql://<<hostip>>:<port>:<sid> (if you have db installed on different box)

Work repository on different database configuration

Similar Messages

Maybe you are looking for