ORA-24334 error after loadSampleData

Answer 1

Hi Stephen,
There is a known issue with reading/writing large CLOBs and double-byte
characters. For the Oracle jDriver in WLS 6.1 sp1 you will need to request two
patches from WLS support ( http://www.bea.com/support/index.jsp ). Request the
patches for CR046149 and CR060917.
Also, verify that your Enterprise Applications use "Use CLOBs for Read" and
"Use CLOBs for Write" = true (this is the out-of-the-box setting for the example
apps). You set these properties in the console (http://<server>:port/console).
For the portal application, you would navigate to Deployments --> Applications
--> portal --> Service Configuration --> JDBC Helper Service.
When the true settings are used the JdbcHelper will read CLOBs using
ResultSet.getClob() and Clob.getCharacterStream(). The JdbcHelper will write
character data to a CLOB field in the database using a
PreparedStatement.setCharacterStream() call for the CLOB field (for the true
setting). If the settings are false then reads are done by using
ResultSet.getString() and writes are done with PreparedStatement.setString().
If the patches do not solve your problem, please re-post.
FYI, the WLCS team is working on a delegate model for the JdbcHelper that
will allow Portal 4.0 to take advantages of database-specific extensions to the
JDBC 2.0 spec for writing CLOBs. The JDBC 2.0 spec does not handle writing data
to CLOBs. Notice that java.sql.Clob has only methods for reading CLOBs. These
extensions to the specification will allow us to stream data directly to the
CLOB instead of inserting character data into the CLOB field in the database.
Watch the release notes for Portal 4.0 at
http://edocs.bea.com/wlp/docs40/relnotes/index.htm for updates.
Stephen Yau wrote:
Hi all,
Just download & install Portal 4.0.... take longgggg time to startup :(.
Anyway, after I get Portal 4.0 up and running, I went thought the
configuration for Oracle, after I ran loadSampleData.bat and restart the
server, I got the following error:
####<2001/11/8 ¤W¤È12®É33¤À46¬í> <Info> <EJB> <fish-mobile> <portalServer>
<main> <system> <> <010008> <EJB Deploying file: placeholder.jar>
####<2001/11/8 ¤W¤È12®É33¤À47¬í> <Info> <EJB> <fish-mobile> <portalServer>
<main> <system> <> <010009> <EJB Deployed EJB with JNDI name
wlcsApp.BEA_personalization.AdConflictResolver.>
####<2001/11/8 ¤W¤È12®É33¤À47¬í> <Info> <EJB> <fish-mobile> <portalServer>
<main> <system> <> <010009> <EJB Deployed EJB with JNDI name
wlcsApp.BEA_personalization.AdBucketService.>
####<2001/11/8 ¤W¤È12®É33¤À47¬í> <Info> <EJB> <fish-mobile> <portalServer>
<main> <system> <> <010009> <EJB Deployed EJB with JNDI name
wlcsApp.BEA_personalization.AdService.>
####<2001/11/8 ¤W¤È12®É33¤À47¬í> <Info> <EJB> <fish-mobile> <portalServer>
<main> <system> <> <010009> <EJB Deployed EJB with JNDI name
wlcsApp.BEA_personalization.PlaceholderService.>
####<2001/11/8 ¤W¤È12®É33¤À48¬í> <Info> <Data Synchronization> <fish-mobile>
<portalServer> <main> <system> <> <000000> <Application: wlcsApp; Data
Repository of type "Placeholder Data Repository" created with persistence
manager of type
"com.bea.p13n.placeholder.internal.PlaceholderPersistenceManager".>
####<2001/11/8 ¤W¤È12®É33¤À51¬í> <Error> <Data Synchronization>
<fish-mobile> <portalServer> <main> <system> <> <000000> <Application:
wlcsApp; Master Data Repository construction failed. Application data will
not be available to services. Please see the following exception and
restart the server.>
Exception[com.bea.p13n.management.data.repository.PersistenceException: An
error ocurred refreshing a Data Repositorys PersistenceManager: {0}] - with
embedded exception:
[Exception[com.bea.p13n.management.data.repository.PersistenceException:
Failed to refresh JDBC Persistence Manager.] - with embedded exception:
[java.sql.SQLException: An IOException has occurred in jdbcHelper.getClob():
Error in getLobStringValue java.sql.SQLException: ORA-24334: ¨S¦³´yz²Åµ¹¦¹
¦ì¸m]]
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.<ini
t>(AbstractDataRepository.java:198)
at
com.bea.p13n.management.data.repository.internal.MasterDataRepository.<init>
(MasterDataRepository.java:46)
at
com.bea.p13n.management.data.repository.DataRepositoryFactory.getMasterDataR
epository(DataRepositoryFactory.java:255)
at
com.bea.p13n.placeholder.internal.PlaceholderServiceImpl.ejbCreate(Placehold
erServiceImpl.java:191)
at
com.bea.p13n.placeholder.internal.PlaceholderServiceImpl_9p0jz2_Impl.ejbCrea
te(PlaceholderServiceImpl_9p0jz2_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.jav
a:153)
at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:191)
at weblogic.ejb20.pool.Pool.onAfterDeploy(Pool.java:172)
at
weblogic.ejb20.deployer.Deployer.runAfterDeploymentListeners(Deployer.java:1
317)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:160)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:279)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:233)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:608)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
92)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:352)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy40.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2734)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:362)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:154)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:608)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
92)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:352)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy56.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
at weblogic.management.Admin.finish(Admin.java:570)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:506)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
Here is the description for ORA-24334:
ORA-24334: no descriptor for this position
Cause: The application is trying to get a descriptor from a handle for an
illegal position.
Action: Check the position number.
The loadSampleData.bat ran fine and didn't report any error. NLS setting
is ZHT16BIG5.
Anyone have any idea?
-Stephen Yau--
Ture Hoefner
BEA Systems, Inc.
2590 Pearl St.
Suite 110
Boulder, CO 80302
www.bea.com