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 !

Similar Messages

Runtime Repository on local database server only

This is a why question, as I have read the installation and configuration guides and don't see this answer. Please forgive me if I've overlooked it.
I am installing OWB in a client/server fashion; the database server resides on a UNIX platform, the client on Windows. I ran the OWB Repository Assistant from my windows desktop, and the repository owner and its objects were created. However, I see in the manual that the OWB Runtime Assistant must run on the same machine where the database resides. I did so, started up the Runtime Assistant on UNIX and created the Runtime Repository into a new user schema, and then a Runtime Access user. All went well.
It looks to me as if both of these wizards create database objects. Why can the Repository Assistant be executed from the desktop environment, but the Runtime Assistant needs to be executed where the database lives, in my case, UNIX. It seems that only database objects are created, it shouldn't matter where the wizard is run from, as long as a database connection can be made.
I feel like I'm missing a piece of the puzzle, can anyone enlighten me. Perhaps a daemon or service is started that I need to know about?

Perhaps a daemon or service is started that I need to know about?That's it! There are some java-services running outside the database. That's e.g. the reason why you can't deploy to an OS/390 system, because these services are not migrated for this JVM yet.
Bye
Detlef
Message was edited by:
289512

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

Rpt-files do not function anymore after deploying to a different database

first: I use CR. 10.2.3600.0 and Asp.NET with Visual Studio 2005
I developed my reports against a Develepment-Database and everything worked fine.
Then, I published my Website with the reports.
Also I made a backup of my Develepment-Database to become the Productive-Database.
All pages of my website function well (database-queries etc.), but when I try to call one of my reports a queerish error message occurs:
"This field name is not known. Error in File C:\WINDOWS\TEMP\...\{...}.rpt: Error in formula. '{xyz.ds_id} = {?@ds_id} and '."
I mean, the database is the "same" as before?!?
(BTW: the logon to the database is set at runtime and is ok.)
Why do the reports not function anymore?
The only workaround I found is to open the report in Visual Studio 2005 again and select "Crystal Reports/Databases/Check Database" against the Productive-Database.
After that the report works! BUT THIS COULD NOT BE THE SOLUTION, this means that I cannot publish my website to a different database on a customers network!!!

I tried this:
Private Sub SetDBLogonForReport(ByVal myConnectionInfo As ConnectionInfo, ByVal myReportDocument As ReportDocument)
        Dim myTables As Tables = myReportDocument.Database.Tables
        ' Get Location of Database from web.config
        Dim Location As String = String.Empty
        Try
            For Each myTable As CrystalDecisions.CrystalReports.Engine.Table In myTables
                Dim myTableLogonInfo As TableLogOnInfo = myTable.LogOnInfo
                myTableLogonInfo.ConnectionInfo = myConnectionInfo
                myTable.Location = myConnectionInfo.DatabaseName & ".dbo." & myTable.Location.Substring(myTable.Location.LastIndexOf(".") + 1)
                myTable.ApplyLogOnInfo(myTableLogonInfo)
            Next
        Catch ex As Exception
            Me.LabelError.Text = "(SetDBLogonForReport) " + ex.Message
        End Try
    End Sub
and get the error:
ex.Message     "Fehler beim Laden der Datenbankinformationen.
Details: Die Datenbank-DLL 'crdb_query.dll' konnte nicht geladen werden.
Fehler in der Datei C:\DOKUME~1\MSCHAE~1\LOKALE~1\Temp\RzpReport {748C95B6-70EC-45B9-953D-64DA215BD9DC}.rpt:
Fehler beim Laden der Datenbankinformationen"
which means in english:
ex.Message     "Error while loading database information.
Details: the databse-dll 'crdb_query.dll' could not be loaded.
Error in file C:\DOKUME~1\MSCHAE~1\LOKALE~1\Temp\RzpReport {748C95B6-70EC-45B9-953D-64DA215BD9DC}.rpt:
Error while loading database information"
I debugged the code and recognized that the error appears while setting the .Location property...?!?
My DatabaseName is "Rezepturverwaltung".
Example 1 with a command:
Befor setting the Location of mytable the value of the prpperty is e.g. "command".
After setting the value like in code above the value changes to "Rezepturverwaltung.dbo.command"
Example 2 with a stored procedure:
Befor setting the Location of mytable the value of the prpperty is e.g. "sp_GetData".
After setting the value like in code above the value changes to "Rezepturverwaltung.dbo.sp_GetData"
What`s going wrong furthermore???
Edited by: Markus Schfer on Aug 31, 2009 9:56 AM

Different runtime in different database

Hi All,
I have one issue which I am doubt about. I have 2 similar user schemas, located in the different database (both are 10G) . I tried to run my SQL query in these 2 user schemas. One of them can run successfully while the another one is hanging there, without knowing when can it be completed. Is there anyone of you have any idea on this? Where can I check in order to rectify the issue?

I have two drivers sitting in two identical looking cars. One is able to start the car and drive off whilst the other is just sitting there. What's the problem?
Answer: It could be one of many things. Lack of petrol, inability of the second person to actually drive. Flat tyres. Elephant standing in front of the car. etc. etc.
So to answer your question, you shouldn't expect the same SQL to run identically on two different databases unless you can ensure the 'different' databases are actually identical in every respect. i.e. they may have the same schema, but do they have the same amount of data. Have they both had statistics gathered to allow the optimiser to pick the most suitable execution plan for both. Are the parameters of database identical for memory requirements, tablespaces, rollback segments etc.
Take a look at When your query takes too long ... and you may gain some insight into where your problem lies.

Different database connections at runtime

How can I change different database connections at runtime on the same Application Module ?
I use BC4J as business layer and uiXml as presentation layer.

Does anyone know how to do this?
I need the same, but i couldn't find any documentation about it.
Looking forward to hearing good news.....

Target Schema and Runtime Instance of Oracle Database

I am new to OWB and starting to understand its architecture.
Does the Runtime Access User, Runtime Repository Schema and Target Schema (discussed a the Runtime Instance) need to be installed on every database that will be a target? For example, if I have a data warehouse and two data marts, with I have three installations?

Hi,
You need to run the OWB Runtime Assistent for every target schema, that is correct (it will add the auditing stuff that enables you to monitor what's happening deployment and execution wise).
Whether you need to create a Runtime Repository and its accompanying Runtime Access User(s) for each and every target I'm not sure.
If your target schema's are on the same instance I'd say that you can use as few or many Runtime Repositories as you wish.
When on different instances I think it's necessary to create them.
Hopefully other forum-attendees can add some more if they have definite answers.
Cheers, Patrick

Process flow execute "complete" in Runtime Audit Browser but it hangs

I create a process flow that contain 4 sub-process flow, each sub-process flow contains several mapping. Each mapping in the process flow will be executed one by one if previous mapping execute successfully. If any error or warning, it will be ended with "End_Error" or "End_Warning". And I deploy the process flow to the workflow server successfully.
Sometimes the process will hang in some certain mapping when execute the process flow. After long time waiting, the status of process flow execution in Audit Browser will be "Complete", but in fact, the sub-porcess ended with that mapping and the next mappings will not be execute. This can be monitored in the Audit browser, as if the whole process "break" at that mapping.
In workflow monitor, I found the workflow has not complete yet. The status of that mapping node is "Notified", not "complete". So I have to abort the workflow in the monitor.
Sometimes when I try again it will be ok. If I deploy the process to another instance that in dw instance, it will also be ok. The dw instance use owb recommend parameters when we install db instance. All the mapping use the default parameters except "Default operation mode", here we use "row based".
Can somebody give me some hint?
Thanks.
OWB 10g rel 1, db: 10g rel2, workflow: 2.6.4

Hi Naidu
Yes you are absolutely right. When you press the cancel button in the GUI, the runtime repository does not get the signal that he is been asked to stop and abort. The GUI cancels himself but the background oracle process is still on !!!. The only way to do is to kill the oracle session. Another way I tried to tackle is
go to the directiry OWB/10.1/owb/rtp/sql and run the file @list_request.sql in sqlplus. Note that you have to login as runtime repositiry owner. After you get the audit id, run the file abort_exec_request.sql and supply the audit id that you obtained by running list_requests.sql. Sometimes it does not work also . Hence the best method is to kill the process

Runtime repository error

Hi,
I have new database. In which i have to update the runtime repository parameters. Actually this database is the clone of existing database.
In the table WB_RT_STORE_PARAMETERS, i have updated the parameter value and parameter name for new database.
Parameter Name: Parameter Value
Schema ID_OWN_DM
host gsunk886h.stex.com
Port 1521
Password password-1
In the old database, the password is an encrypted one and it will be like something like ??$$||&?
But now, actual password is displaying. So when i try to deploy the mapping i am getting the following error.
Create Failed Create RPE-01003: An infrastructure condition prevented the request from completing.
- ORA-28232: invalid input length for obfuscation toolkit
ORA-06512: at "SYS.DBMS_OBFUSCATION_TOOLKIT_FFI", line 40
ORA-06512: at "SYS.DBMS_OBFUSCATION_TOOLKIT", line 153
ORA-06512: at "ID_OWN_PSRT.WB_RT_SERVICE_CONTROL", line 254
Kindly help,
Sasi

Hi,
I have new database. In which i have to update the runtime repository parameters. Actually this database is the clone of existing database.
In the table WB_RT_STORE_PARAMETERS, i have updated the parameter value and parameter name for new database.
Parameter Name: Parameter Value
Schema ID_OWN_DM
host gsunk886h.stex.com
Port 1521
Password password-1
In the old database, the password is an encrypted one and it will be like something like ??$$||&?
But now, actual password is displaying. So when i try to deploy the mapping i am getting the following error.
Create Failed Create RPE-01003: An infrastructure condition prevented the request from completing.
- ORA-28232: invalid input length for obfuscation toolkit
ORA-06512: at "SYS.DBMS_OBFUSCATION_TOOLKIT_FFI", line 40
ORA-06512: at "SYS.DBMS_OBFUSCATION_TOOLKIT", line 153
ORA-06512: at "ID_OWN_PSRT.WB_RT_SERVICE_CONTROL", line 254
Kindly help,
Sasi

Where is the runtime repository assistant???

Hi all,
I am working with the OBI SE.
When I am deploying the objects I am getting an error because there is not a valid runtime repository. I found that I have to create the runtime schema with the runtime repository assistant but I don't find it in the menu.
Someone knows if it is installed with OBISE? What do I have to do to create the runtime schema? or, it is already created with the installation?
Many thanks in advance,
Victor.

The runtime repository is a part of OWB repository. It's not related to OBISE.
So, I'm assuming your question regarding the Runtime Repository is related to Oracle Warehouse Builder.
It seems like you've created the Design Rep, but did not created the runtime. This is not possible to achieve, unless you explicitly create like that.
You should run the OWB Repository Assistant and choose the BASIC INSTALL option, if you are using OWB on the same box as the database server.
Please, provide more details about your servers and software architecture, versions, os versions and releases.
Best wishes,
Marcos

About the runtime repository?

Hi,
I'm confused by the runtime repository?
what was stored in the runtime repository when i deployed a map to a location?
i have two warehouse targets in my owb project.when i was deploying a map,a error occured.
following was the error description:
"Cannot deploy to the target location because it is owned by a different runtime platform."
the map is used to load data from one table in a target warehouse to a table in another target warehouse.
who can tell me the reason? thanks in advance!

Hi,
The runtime repository owns a set of targets. So for each target you can deploy only using the runtime repository that has this target schema registered to it.
It sounds like your target schema is therefore not managed by this runtime repository. You would have to register the target schema to this repository using the runtime assistant. Simply install a target into the existing target user.
Jean-Pierre

Install OWB Runtime user on other DB than runtime repository

hello all
Is it possible to install a runtime user on a different database than on which the owb runtime repository is installed? The OWB version we currently use is the 9.2.0.2 version so no Paris feature replies please.
I think so but my DBA which doesn't know and doesn't give me the rights to do so on test is not convinced he can do so. Please point me out to a doc that clearly states we should be able to do this.
Thanks in advance.
Koen

Hi
Yes, just install another runtime repository on the new database. Then use that repository for all jobs on that database.
Cheers Ian

Why we need Design Repository and Runtime repository seperately?

Hi All,
Anybody please tell me why we need design time repository and runtime repository seperately? And also I want to know the total OWB Architecture.
Thanks,
Siv
Edited by: Siv on Feb 10, 2010 10:40 PM

Hi Siv:
Concerning Repository:
Since OWB 10.2 there is only one Repository storing Design and Runtime-Components.
excerpt from http://download.oracle.com/docs/cd/E10926_01/doc/owb.101/b12146/over.htm (OWB 10.1.):
The Design Repository, installed in an Oracle database, stores the metadata definitions for all of the objects used in Warehouse Builder. This is where all of the design information is stored for the target systems you are creating. You can access metadata stored here using the client user-interface, or through OMB Plus, the Warehouse Builder scripting utility.
The runtime repository, installed in an Oracle database, stores all of the deployment data as well as data from executed mappings and process flows. This is where the target environment information is stored for the business intelligence systems you create. This includes connection information for all of the deployment locations.
Which version of OWB are you using?
Greetings
Guenther Herzog

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)
          >

Can we use different Databases (Oracle & SQL Server) in one report?

Post Author: venki5star
CA Forum: .NET
Hi there.
Can we use different databases (Oracle & SQL Server) in a same report?
If possible how?
Another question,
Can we change the Provider Name at runtime of the given report. If so the above question is useless...
Thanks in Advance.

I tried this using Oracle Provider for OLEDB (the one that supplied by Oracle Client) and Crystal Reports 9. you can drag the column into designer but the image does not appear in preview.
I guess it's because CR does not recognized it as image, and there are no information that the blob data is an image at all.

Deployment to runtime repository in different database hangs

Similar Messages

Maybe you are looking for