AIA Deployment Failed After Patching

Hi Oracle Community,
We have a AIA purchase order interface. The interface itself has about 8 composites. We have been successfully using the following process to deploy the interface for the past 12 months:
ant -f $AIA_HOME/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=$AIA_HOME/deploy/purchaseorder/PurchaseOrderInterfaceDP.xml -DPropertiesFile=$AIA_HOME/aia_instances/<instance_name>/config/AIAInstallProperties.xml
However, we have recently applied patch 'AIA 11.1.1.6 Rollup Patch 5 – Patch 17423167' to our Weblogic 11.1.1.6 environment. Since then we get the error below when attempting to deploy this AIA interface.
BUILD FAILED
/oracle/product/Middleware/AIA/Infrastructure/Install/AID/AIAExecuteDriver.xml:118: The following error occurred while executing this line:
/oracle/product/Middleware/AIA/Infrastructure/Install/AID/AIAExecuteDriver.xml:65: The following error occurred while executing this line:
/oracle/product/Middleware/AIA/aia_instances/AIA_TEST/tmp/AIDExecuteDP_temp_1308451709.xml:4: Unknown attribute [partition]
Note that we are unable to deploy any of our AIA interfaces using this method since patching.
Has anyone come across this problem?
Hoang

After further investigations, we removed the partition reference from the deployment script thereby deploying to the default partition and deployment was successful.
I passed this knowledge onto sysadmins and a partition configuration step was missed. After configuration, deployment worked successfully as per prepatching.
Hoang

Similar Messages

Smc fails after patching

Good evening
Running a freshly installed 11/06 build of solaris 10 x86, I don't have any issues with smc. Immediately after patching, installing all recommended patches, smc so longer starts up.
bash-3.00# smc
Warning: Cannot convert string "-monotype-arial-regular-r-normal--*-140-*-*-p-*-iso8859-1" to type FontStruct
Warning: Unable to load any usable ISO8859-1 font
Warning:
Name: FONTLIST_DEFAULT_TAG_STRING
Class: XmRendition
Conversion failed. Cannot load font.
Java Accessibility Bridge for GNOME loaded.
java.lang.InternalError: java/langNullPointerException
at sun.awt.motif.MComponentPeer.pSetFont(Native Method)
at sun.awt.motif.MComponentPeer.setFont(MComponentPeer.java:247)
at sun.awt.motif.MWindowPeer.init(MWindowPeer.java:116)
at sun.awt.motif.MFramePeer.<init>(MFramePeer.java:58)
at sun.awt.motif.MToolkit.createFrame(MToolkit.java:231)
at java.awt.Frame.addNotify(Frame.java:491)
at java.awt.Window.addNotify(Window.java:462)
at java.awt.Window.show(Window.java:514)
at com.sun.management.viper.console.gui.VSplashScreen.show(VSplashScreen.java:166)
at com.sun.management.viperimpl.console.BaseConsoleOptionsManager.openConsole(BaseConsoleOptionsManager.java:746)
at com.sun.management.viperimpl.console.BaseConsoleOptionsManager.redirectToConsole(BaseConsoleOptionsManager.java:648)
at com.sun.management.viperimpl.console.BaseConsoleOptionsManager.launchConsole(BaseConsoleOptionsManager.java:173)
at com.sun.management.viperimpl.console.BaseConsoleOptionsManager.main(BaseConsoleOptionsManager.java:861)
I'm guessing that something got horked up during patching, however, I'm not really sure which one(s) might have done so. Anyone have any ideas?
-Matt

I'm more familiar with the similarly-named Sun Management Center, but I think this may be a Java compatibility issue: possibly the patched version requires a later version of java. It would help to know which version's in your environment (java -version).

MDT 2013 Server 2012 R2 Core Deployment Fails After Disabling ChecksumOffloads on NICs

When changes are made to the Checksum offloads, the NICs reset themselves and I'm losing connectivity to the deployment share during the deployment process (LiteTouch). It happens during a custom PowerShell script I'm running in the Task Sequence
after "Tattoo".
PowerShell Script:
Disable-NetAdapterChecksumOffload -Name * -IpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv4
Disable-NetAdapterChecksumOffload -Name * -UdpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv6
Disable-NetAdapterChecksumOffload -Name * -UdpIPv6
Disable-NetAdapterLso -Name * -IPv4
Disable-NetAdapterLso -Name * -IPv6
Disable-NetAdapterRss -Name *
Here are the errors from the BDD.log (sorry couldn't get the _SMSTaskSequence.log)
ZTIPowerShell processing completed successfully. ZTIPowerShell 8/25/2014 2:27:28 PM 0 (0x0000)
Command completed, return code = -2147467259 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259 0x80004005 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
For more information, consult the task sequencer log ...\SMSTS.LOG. LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
Property RetVal is now = -2147467259 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
Unable to copy log to the network as no SLShare value was specified. LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
What I was thinking about trying was adding a few lines to the end of my script:
1. PING 1.1.1.1 -n 1 -w 30000 >NUL
    This would give the server 30 seconds to right itself after resetting the NICs
2. net use command to remap the share.
Two questions regarding re-mapping the share.
   1. I'm assuming this will run as Administrator token. Will this be an issue for continued deployment?
   2. At the beginning of the deployment process the Tech has to enter his/her credentials to access the deployment share to begin the deployment process. Are those the credentials I need to continue using, or does MDT use some other credentials
to access the deployment share that far into the deployment process (during state restore phase)?
Thank you for taking time to read my post.
-Cheers!

Apologies for the delay in responding to this thread.
It turns out that Broadcom NICs are the culprit!
For some reason Broadcom doesn't grant you access to all the feature sets on their NICs when it comes to PowerShell.
Same script runs against Intel NICs with no issues.
I placed a 15 second pause in the script to allow NICs to reset, I then remap MDT network drive to continue the deployment process. Big thanks to Keith for assisting with reconnecting the network drive!
Here is the script I settled on:
# All settings will not take, if target is using Broadcom NICs.
# You will still need to manually set TCP IPv4 and IPv6 to disabled.
# Commands to disable Checksum Offloads.
Disable-NetAdapterChecksumOffload -Name * -IpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv4
Disable-NetAdapterChecksumOffload -Name * -UdpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv6
Disable-NetAdapterChecksumOffload -Name * -UdpIPv6
Disable-NetAdapterLso -Name * -IPv4
Disable-NetAdapterLso -Name * -IPv6
Disable-NetAdapterRss -Name *
# Pause script for 15 seconds to allow ample time for NICs to reset.
Start-Sleep -s 15
net use %DeployRoot% /u:"%UserDomain%\%UserID%" "%USerPassword%"
# Pause script end for 5 seconds to allow completion of share recreation.
Start-Sleep -s 5

Deployment failing after filer migration in weblogic

Hi, We have used weblogic on Netapps Filer, recently we migrated from Netapps to Sun filer and after this deployment issue came up. The deployment fails for 2-3 times with the following error "java.lang.NoClassDefFoundError: flex/messaging/license/AsnDecoder" and after that it deploys successfully.
We have used Netapps for more than 3 years without any deployment issues.
Can someone please let us know if you faced such problem...and what was the resolution.

"java.lang.NoClassDefFoundError: flex/messaging/license/AsnDecoder"
This indicates that the 'deployment' is missing the class that it uses for something.
What you need to do is find the .jar file that includes the class. After some Googling it is found that flex-messaging-req.jar contains the class ( Download flex-messaging-data-req.jar : flex&nbsp;&laquo;&nbsp;f&nbsp;&laquo;&nbsp;Jar File Down…) - hope it is the right version.

Non priviledged commands fail after patch cluster install

For several years, to allow users to access system functions for higher clock resolutions in their
applications, we have made the following mods to two files (per Sun recommendations):
In the /etc/system file, add lines:
* 10 ms clock resolution*
set higher_tick = 1*
In /etc/user_attr, add:
dssuser::::type=normal;defaultpriv=proc_clock_highres,file_link_any,proc_info,proc_session,proc_fork,proc_exec
Everything was fine until I installed the latest patch cluster (from 2-14-2011) on our Netra 210. No issues installing the cluster. Upon reboot, the dssuser cannot do some simple things, like use ftp or ping. Messages like this:
ping: unknown host
ftp: socket: Permission denied.
The root user has no problems using any of these commands. As soon as I comment out the dssuser line from the /etc/user_attr file, everything works as expected. But we need the highres clock settings for our applications. I am unfamiliar with the workings and intent of the entries in user_attr so any help would be most appreciated.
Mark

The problem is that after patch implementation, the special privileges for any user defined in the /etc/user_attr file were modified to append the string "!net_privaddr" specifically denying use of common commands ping and ftp for example. The output of ppriv:
$ ppriv $$
14870: -sh
flags = <none>
E: basic,proc_clock_highres,!net_privaddr
I: basic,proc_clock_highres,!net_privaddr
P: basic,proc_clock_highres,!net_privaddr
L: all
I had to add the keyword net_privaddr in the user_attr file like:
dssuser::::type=normal;defaultpriv=proc_clock_highres,file_link_any,proc_info,proc_session,proc_fork,proc_exec,net_privaddr
to get past this problem. A bug or what?

Deploy fails after move of ABAP&JAVA stack to other server

Hello,
We moved our system (ABAP&JAVA) to a new server with exactly the same OS level and configuration by means of online backup and restore.
Installation details are:
SOLARIS 9
SAP ECC5 SP12
Java stack SP16
After the move the ABAP and the Portal is ok.The server,dispatcher and SDM are also starting fine and no errors shown in the trace files.
Problem is when trying to run&deploy any example application of the J2EE engine it fails with the following error:
Application error occurred during request processing.
Details: java.rmi.RemoteException: Cannot commit handler in
operation deploy with application sap.com/Calculator..
Reason: Error occurred during DB access:
apps/sap.com/Calculator/servlet_jsp, ; nested exception is:
com.sap.engine.frame.core.configuration.ConfigurationException:
Error occurred during DB access: apps/sap.com/Calculator/servlet_jsp,
Exception id: [0003BAC828490049000000240000582F000419144C86546C]
Did you encountered such an issue?
Is there anything special to do for the SDM when moving to a different server? We simply restored from tape the filesystem containing the SDM and the J2EE folders.
Thanks a lot for your help,
Kind Regards,
Florin

Hello All,
Please ignore the question; issue is fixed in the mean time.
Reason was that after the restore the temporary tablespace had no file so this caused the deploy to fail
Regards,
Florin

FTP adapter deployment failed after restart of the server

Hi,
I have a single node 11g server. I had created some outbound connection pools for the ftp adapter. When I created them they were working fine.
But after the restart of the server the FTP Adapter state in the summary of deployment page is showing failed. The error I am getting is below
<Unable to set the activation state to true for the application 'FtpAdapter'.
java.lang.NoClassDefFoundError: oracle/tip/adapter/file/FileLogger
     at oracle.tip.adapter.ftp.FTPManagedConnectionFactory.createConnectionFactory(FTPManagedConnectionFactory.java:154)
     at weblogic.connector.security.layer.AdapterLayer.createConnectionFactory(AdapterLayer.java:787)
     at weblogic.connector.outbound.ConnectionPool.getConnectionFactory(ConnectionPool.java:2013)
     at weblogic.connector.outbound.RAOutboundManager.activatePool(RAOutboundManager.java:1076)
     at weblogic.connector.outbound.RAOutboundManager.activate(RAOutboundManager.java:183)
     at weblogic.connector.common.RAInstanceManager.activate(RAInstanceManager.java:437)
     at weblogic.connector.deploy.ConnectorModule.activate(ConnectorModule.java:303)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
     at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
####<Apr 6, 2011 4:02:24 PM IST> <Error> <Deployer> <inhysu01> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000IweNRSu8TsO8mjGNtn1Db43e000001> <1302085944811> <BEA-149250> <Unable to unprepare application 'FtpAdapter'.
weblogic.application.ModuleException: Error occurred while trying to rollback the module: weblogic.connector.exception.RAException:
There are 1 nested errors:
There are 1 nested errors:
ObjectLifeCycleException: weblogic.common.resourcepool.ObjectLifeCycleException: Attempted to shutdown the pool eis/Ftp/FtpAdapter when it is currently not in SUSPENDED state (Running)
     at weblogic.common.resourcepool.ResourcePoolImpl.shutdown(ResourcePoolImpl.java:299)
     at weblogic.connector.outbound.ConnectionPool.shutdown(ConnectionPool.java:355)
     at weblogic.connector.outbound.RAOutboundManager.internalShutdownPool(RAOutboundManager.java:346)
     at weblogic.connector.outbound.RAOutboundManager.rollback(RAOutboundManager.java:305)
     at weblogic.connector.common.RAInstanceManager.rollbackRAOutboundMgr(RAInstanceManager.java:623)
     at weblogic.connector.common.RAInstanceManager.rollback(RAInstanceManager.java:566)
     at weblogic.connector.deploy.ConnectorModule.unprepare(ConnectorModule.java:268)
     at weblogic.application.internal.flow.ModuleListenerInvoker.unprepare(ModuleListenerInvoker.java:285)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.previous(DeploymentCallbackFlow.java:523)
     at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
     at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.unprepare(DeploymentCallbackFlow.java:211)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.unprepare(DeploymentCallbackFlow.java:202)
     at weblogic.application.internal.BaseDeployment$1.previous(BaseDeployment.java:619)
     at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
     at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
     at weblogic.application.internal.BaseDeployment.unprepare(BaseDeployment.java:248)
     at weblogic.application.internal.SingleModuleDeployment.unprepare(SingleModuleDeployment.java:43)
     at weblogic.application.internal.DeploymentStateChecker.unprepare(DeploymentStateChecker.java:205)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.unprepare(AppContainerInvoker.java:117)
     at weblogic.deploy.internal.targetserver.BasicDeployment.unprepare(BasicDeployment.java:287)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:363)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
     at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Can anyone please help me with this.
Thanks in advance

The solution is either change the order of deployment or copy the FileAdapter.rar file in $ORACLE_HOME/lib location and restart the server as mentioned here.
http://soa-bpel-esb.blogspot.com/2011/04/javalangnoclassdeffounderror.html

Rebuilding spatial indexing fail after patch 9.2.0.8.0

Hi!
I did apply patchset, and after i did try to
set NLS_LANG=American_America.CL8MSWIN1251
sqlplusw ......
SQL> alter index XXXX.YYYYYYYY_g_idx rebuild; -- <- Russian name
alter index XXXX.YYYYYYYY_g_idx rebuild
ERROR at line 1:
ORA-29858: error occurred in the execution of ODCIINDEXALTER routine
ORA-29400: data cartridge error
¡a¤
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13205: internal error while parsing spatial parameters
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 259
ORA-06512: at line 1
As you can see, rebuilding was failed.
Before upgrade all did work fine.
If i will create table WITH_ENGLISH_NAME as SELECT from my table all working fine ;(
I DID apply all *.sql from patchset.
Any idea, gurus ?
P.S.
I did use script from metalink
verify_spatial_installation.sql :
SQL>
SQL> prompt Verify version and status
Verify version and status
SQL> select COMP_NAME, SCHEMA, VERSION, STATUS
2 from dba_registry where comp_id='SDO';
COMP_NAME SCHEMA VERSION STATUS
Spatial MDSYS 9.2.0.8.0 VALID
SQL>
SQL> prompt Number of objects
Number of objects
SQL> select count(*)
2 from dba_objects where owner='MDSYS';
COUNT(*)
250
SQL>
SQL> prompt Summary count of objects
Summary count of objects
SQL> select object_type, count(*)
2 from dba_objects where owner='MDSYS'
3 group by object_type;
OBJECT_TYPE COUNT(*)
FUNCTION 47
INDEX 17
INDEXTYPE 2
LIBRARY 12
LOB 12
OPERATOR 14
PACKAGE 25
PACKAGE BODY 25
SEQUENCE 2
TABLE 18
TRIGGER 7
TYPE 34
TYPE BODY 10
VIEW 25
14 rows selected.
SQL>
SQL> prompt Any invalid objects ?
Any invalid objects ?
SQL> select object_name, object_type, status
2 from dba_objects
3 where owner='MDSYS'
4 and status <> 'VALID'
5 order by object_name;
OBJECT_NAME OBJECT_TYPE STATUS
SDO_MIGRATE PACKAGE BODY INVALID
SQL>
SQL> prompt List of all spatial objects ordered by object_name
List of all spatial objects ordered by object_name
SQL> select object_name, object_type, status
2 from dba_objects where owner='MDSYS'
3 order by object_name;
OBJECT_NAME OBJECT_TYPE STATUS
AGGRCENTROID TYPE VALID
AGGRCENTROID TYPE BODY VALID
AGGRCONVEXHULL TYPE VALID
AGGRCONVEXHULL TYPE BODY VALID
AGGRLRSCONCAT TYPE VALID
AGGRLRSCONCAT TYPE BODY VALID
AGGRLRSCONCAT3D TYPE VALID
AGGRLRSCONCAT3D TYPE BODY VALID
AGGRMBR TYPE VALID
AGGRMBR TYPE BODY VALID
AGGRUNION TYPE VALID
AGGRUNION TYPE BODY VALID
ALL_GEOMETRY_COLUMNS VIEW VALID
ALL_SDO_GEOM_METADATA VIEW VALID
ALL_SDO_INDEX_INFO VIEW VALID
ALL_SDO_INDEX_METADATA VIEW VALID
ALL_SDO_LRS_METADATA VIEW VALID
ALL_SDO_MAPS VIEW VALID
ALL_SDO_STYLES VIEW VALID
ALL_SDO_THEMES VIEW VALID
CS_SRS TABLE VALID
DBA_GEOMETRY_COLUMNS VIEW VALID
DBA_SDO_INDEX_INFO VIEW VALID
DBA_SDO_INDEX_METADATA VIEW VALID
DBA_SDO_LRS_METADATA VIEW VALID
DBA_SDO_MAPS VIEW VALID
DBA_SDO_STYLES VIEW VALID
DBA_SDO_THEMES VIEW VALID
F81_INDEX_OBJECT TYPE VALID
F81_INDEX_OBJ_ARRAY TYPE VALID
F81_NT_IND_TYPE TYPE VALID
GEOCODER_HTTP PACKAGE VALID
GEOCODER_HTTP PACKAGE BODY VALID
GEOCODE_RESULT TYPE VALID
GEODETIC_SRIDS VIEW VALID
H81_INDEX_OBJECT TYPE VALID
H81_INDEX_OBJ_ARRAY TYPE VALID
H81_NT_IND_TYPE TYPE VALID
HHAND FUNCTION VALID
HHBYTELEN FUNCTION VALID
HHCBIT FUNCTION VALID
HHCELLBNDRY FUNCTION VALID
HHCELLSIZE FUNCTION VALID
HHCLDATE FUNCTION VALID
HHCOLLAPSE FUNCTION VALID
HHCOMMONCODE FUNCTION VALID
HHCOMPARE FUNCTION VALID
HHCOMPOSE FUNCTION VALID
HHDECODE FUNCTION VALID
HHDISTANCE FUNCTION VALID
HHENCODE FUNCTION VALID
HHENCODE_BYLEVEL FUNCTION VALID
HHGBIT FUNCTION VALID
HHGETCID FUNCTION VALID
HHGROUP FUNCTION VALID
HHGTBIT FUNCTION VALID
HHGTYPE FUNCTION VALID
HHIDLPART FUNCTION VALID
HHIDPART FUNCTION VALID
HHINCRLEV FUNCTION VALID
HHJLDATE FUNCTION VALID
HHLENGTH FUNCTION VALID
HHLEVELS FUNCTION VALID
HHMATCH FUNCTION VALID
HHMAXCODE FUNCTION VALID
HHNCOMPARE FUNCTION VALID
HHNDIM FUNCTION VALID
HHOR FUNCTION VALID
HHORDER FUNCTION VALID
HHPRECISION FUNCTION VALID
HHSBIT FUNCTION VALID
HHSETCID FUNCTION VALID
HHSTBIT FUNCTION VALID
HHSTYPE FUNCTION VALID
HHSUBDIVIDE FUNCTION VALID
HHSUBSTR FUNCTION VALID
HHXOR FUNCTION VALID
LOCATOR_WITHIN_DISTANCE OPERATOR VALID
MD PACKAGE VALID
MD PACKAGE BODY VALID
MD$RELATE TABLE VALID
MD1 PACKAGE VALID
MD1 PACKAGE BODY VALID
MD2 PACKAGE VALID
MD2 PACKAGE BODY VALID
MDERR PACKAGE VALID
MDERR PACKAGE BODY VALID
MDPRVT_IDX PACKAGE VALID
MDPRVT_IDX PACKAGE BODY VALID
MD_LRS PACKAGE VALID
MD_LRS PACKAGE BODY VALID
OGIS_GEOMETRY_COLUMNS TABLE VALID
OGIS_SPATIAL_REFERENCE_SYSTEMS TABLE VALID
ORDMD_AG_LIBS LIBRARY VALID
ORDMD_CS_LIBS LIBRARY VALID
ORDMD_IDX_LIBS LIBRARY VALID
ORDMD_LRS_LIBS LIBRARY VALID
ORDMD_MBR_LIBS LIBRARY VALID
ORDMD_MIG_LIBS LIBRARY VALID
ORDMD_PRIDX_LIBS LIBRARY VALID
ORDMD_REL_LIBS LIBRARY VALID
ORDMD_RTREE_LIBS LIBRARY VALID
ORDMD_UDT_LIBS LIBRARY VALID
ORDMD_UTL_LIBS LIBRARY VALID
ORDMD_WD_LIBS LIBRARY VALID
PK_SDO_MASK INDEX VALID
PK_SRID INDEX VALID
PRVT_IDX PACKAGE VALID
PRVT_IDX PACKAGE BODY VALID
RTREE_FILTER OPERATOR VALID
RTREE_IDX PACKAGE VALID
RTREE_IDX PACKAGE BODY VALID
RTREE_INDEX INDEXTYPE VALID
RTREE_INDEX_METHOD TYPE VALID
RTREE_INDEX_METHOD TYPE BODY VALID
RTREE_NN OPERATOR VALID
SAMPLE_SEQ SEQUENCE VALID
SDO PACKAGE VALID
SDO PACKAGE BODY VALID
SDOAGGR TYPE VALID
SDOAGGR TYPE BODY VALID
SDOAGGRTYPE TYPE VALID
SDO_3GL PACKAGE VALID
SDO_3GL PACKAGE BODY VALID
SDO_ADMIN PACKAGE VALID
SDO_ADMIN PACKAGE BODY VALID
SDO_AGGR_CENTROID FUNCTION VALID
SDO_AGGR_CONVEXHULL FUNCTION VALID
SDO_AGGR_LRS_CONCAT FUNCTION VALID
SDO_AGGR_LRS_CONCAT_3D FUNCTION VALID
SDO_AGGR_MBR FUNCTION VALID
SDO_AGGR_UNION FUNCTION VALID
SDO_ANGLE_UNITS TABLE VALID
SDO_AREA_UNITS TABLE VALID
SDO_CATALOG PACKAGE VALID
SDO_CATALOG PACKAGE BODY VALID
SDO_CONSTRUCT_DIM_ARRAY FUNCTION VALID
SDO_CS PACKAGE VALID
SDO_CS PACKAGE BODY VALID
SDO_DATUMS TABLE VALID
SDO_DIM_ARRAY TYPE VALID
SDO_DIM_ELEMENT TYPE VALID
SDO_DIST_UNITS TABLE VALID
SDO_DROP_USER TRIGGER VALID
SDO_ELEM_INFO_ARRAY TYPE VALID
SDO_ELLIPSOIDS TABLE VALID
SDO_FILTER OPERATOR VALID
SDO_GEOM PACKAGE VALID
SDO_GEOM PACKAGE BODY VALID
SDO_GEOMETRY TYPE VALID
SDO_GEOMETRY TYPE BODY VALID
SDO_GEOM_IDX INDEX VALID
SDO_GEOM_METADATA_TABLE TABLE VALID
SDO_GEOM_TRIG_DEL1 TRIGGER VALID
SDO_GEOM_TRIG_INS1 TRIGGER VALID
SDO_GEOM_TRIG_UPD1 TRIGGER VALID
SDO_IDX PACKAGE VALID
SDO_IDX PACKAGE BODY VALID
SDO_IDX_MDATA_IDX INDEX VALID
SDO_IDX_TAB_SEQUENCE SEQUENCE VALID
SDO_INDEX_METADATA_TABLE TABLE VALID
SDO_INDEX_METHOD_9I TYPE VALID
SDO_INDEX_METHOD_9I TYPE BODY VALID
SDO_INT2_FILTER OPERATOR VALID
SDO_INT2_RELATE OPERATOR VALID
SDO_INT_FILTER OPERATOR VALID
SDO_INT_RELATE OPERATOR VALID
SDO_LRS PACKAGE VALID
SDO_LRS PACKAGE BODY VALID
SDO_LRS_METADATA_TABLE TABLE VALID
SDO_LRS_META_IDX INDEX VALID
SDO_LRS_TRIG_DEL TRIGGER VALID
SDO_LRS_TRIG_INS TRIGGER VALID
SDO_LRS_TRIG_UPD TRIGGER VALID
SDO_MAPS_TABLE TABLE VALID
SDO_MBR TYPE VALID
SDO_META PACKAGE VALID
SDO_META PACKAGE BODY VALID
SDO_MIGRATE PACKAGE VALID
SDO_MIGRATE PACKAGE BODY INVALID
SDO_NN OPERATOR VALID
SDO_NN_DISTANCE OPERATOR VALID
SDO_NUMTAB TYPE VALID
SDO_ORDINATE_ARRAY TYPE VALID
SDO_POINT_TYPE TYPE VALID
SDO_PRIDX PACKAGE VALID
SDO_PRIDX PACKAGE BODY VALID
SDO_PROJECTIONS TABLE VALID
SDO_RELATE OPERATOR VALID
SDO_RELATEMASK_TABLE VIEW VALID
SDO_RELATE_MASK PACKAGE VALID
SDO_RELATE_MASK PACKAGE BODY VALID
SDO_RID_ARRAY TYPE VALID
SDO_RTREE_ADMIN PACKAGE VALID
SDO_RTREE_ADMIN PACKAGE BODY VALID
SDO_RTREE_FILTER OPERATOR VALID
SDO_RTREE_RELATE OPERATOR VALID
SDO_STAT TYPE VALID
SDO_STATTAB TYPE VALID
SDO_STYLES_TABLE TABLE VALID
SDO_THEMES_IDX INDEX VALID
SDO_THEMES_TABLE TABLE VALID
SDO_TUNE PACKAGE VALID
SDO_TUNE PACKAGE BODY VALID
SDO_UTIL PACKAGE VALID
SDO_UTIL PACKAGE BODY VALID
SDO_VERSION FUNCTION VALID
SDO_VPOINT_TYPE TYPE VALID
SDO_WITHIN_DISTANCE OPERATOR VALID
SPATIAL_INDEX INDEXTYPE VALID
SYS_C001565 INDEX VALID
SYS_C001571 INDEX VALID
SYS_C001706 INDEX VALID
SYS_LOB0000027008C00040$$ LOB VALID
SYS_LOB0000027008C00041$$ LOB VALID
SYS_LOB0000027053C00012$$ LOB VALID
SYS_LOB0000027053C00013$$ LOB VALID
SYS_LOB0000027209C00004$$ LOB VALID
SYS_LOB0000027216C00005$$ LOB VALID
SYS_LOB0000027216C00006$$ LOB VALID
SYS_LOB0000027216C00013$$ LOB VALID
SYS_LOB0000027216C00014$$ LOB VALID
SYS_LOB0000027229C00006$$ LOB VALID
SYS_LOB0000028651C00012$$ LOB VALID
SYS_LOB0000028651C00013$$ LOB VALID
TRANSFORM_MAP PACKAGE VALID
TRANSFORM_MAP PACKAGE BODY VALID
UNIQUE_ANGLE_UNITS INDEX VALID
UNIQUE_AREA_UNITS INDEX VALID
UNIQUE_DIST_UNITS INDEX VALID
UNIQUE_LAYERS INDEX VALID
UNIQUE_MAPS INDEX VALID
UNIQUE_STYLES INDEX VALID
UNIQUE_TABLES INDEX VALID
UNIQUE_THEMES INDEX VALID
USER_CS_SRS TABLE VALID
USER_GEOMETRY_COLUMNS VIEW VALID
USER_SDO_GEOM_METADATA VIEW VALID
USER_SDO_INDEX_INFO VIEW VALID
USER_SDO_INDEX_METADATA VIEW VALID
USER_SDO_LRS_METADATA VIEW VALID
USER_SDO_MAPS VIEW VALID
USER_SDO_STYLES VIEW VALID
USER_SDO_THEMES VIEW VALID
USER_TRANSFORM_MAP TABLE VALID
V81_INDEX_OBJECT TYPE VALID
V81_INDEX_OBJ_ARRAY TYPE VALID
V81_NT_IND_TYPE TYPE VALID
VERTEX_SET_TYPE TYPE VALID
VERTEX_TYPE TYPE VALID
250 rows selected.
SQL>
SQL> spool off

Sir! No Sir! :)
I will try to explain.
If I do have table with russian letter, than creating index creation will fail, no matter name of index :(
But if I will prepare copy of my table with english name (including meta-data) - index creations is succesfull.

ZCM 11 Remote Management Policy Failed after Patch 2

Upgraded to Cumulative Agent Patch 2 on ZCM 11 and now my remote management policy fails. It keeps stating that it "Could not find a results file for remote management policy...."
Is anyone else having this issue?

Dpogue,
This is being worked on, it's not related to the agent update as far as
we know - TID 7006354 has some details.
Shaun Pond

MDT image deployment fails after adding applications

I've been trying to use MDT (ie deployment workbench 6.2.5019.0) to build and deploy images for quite some time now, and I am having a lot of difficulty deploying images to target computers. I've successfully built a reference image in a VM with all
the Win7 updates. I can deploy that image to HP z820 workstations while injecting drivers. Then I've tried two ways of adding applications, capturing that image and then re-deploying it to other target machines.
First, I run a standard client task sequence that will deploy and capture an image to a target machine. I put in a suspend command in the task sequence. I can then add applications and then restart the task sequence. If I don't add applications,
and I just let the task sequence do it's magic, inject drivers, add any remaining Windows updates, and then just resume, MDT will capture the image. I can then add it to my deployment share and then deploy it back to my target machine that it came from
or any other similar target. On the other hand, if I add all my applications during the suspend, MDT will capture the image, but subsequent deployments of the image will always fail on the target machine during Windows setup.
Second, I can deploy the reference image to a target, let the sequence finish, add the apps, then run a sysprep and capture task sequence. I finally got that to work. I have an image with apps that I can deploy. However, I go to a target
machine that image was deployed to, I added for example Office and Winzip. Then I run the same sysprep and capture sequence, capture the image, and when I deploy that image back, it hangs while setup is installing devices.
Why am I having so much trouble just adding applications to an image that deployed perfectly fine before, but once I add apps, I can no longer use the same task sequences to capture and deploy? These same task sequences will capture and deploy the
image without the apps, but not with the apps. I don't get it.
So, what's so special about adding applications, and also can anyone give me a good reference for troubleshooting deployment issues where sysprep and setup fail for whatever reason?

Hmmm... Applications should not cause hangs when installing drivers. In fact NOTHING should cause a hang like that... except for a bad driver. Go back and go through you driver manifest with a fine tooth comb and find the bad driver. That may include removing
all of your 3rd party drivers.
Keith Garner - keithga.wordpress.com

Admin password fails after patch and reboot.

Hi,
Is there a way to resolve the issue of the admin password after applying a patch 117667-06 and rebooting the system.
Both the Sun One Administration Server 5.2 and Sun ONE Directory Server 5.2 services are running in Services.
I was able to login to the Server console prior to the patch, and to install the patch which requires the mentioned password.
Cannot connect to Admin Server 'http://servername:20000". The URL is incorrect or the server is not responding."
Thanks.

Can you please share what the solution was? Might be useful to other readers in the future.

Deployment fails after ESS import

I want to modify an ESS application using NWDI.
I have setup NW2004s SP11 with NWDI and imported ESS SP8, PCUI_GP SP8.
In NWDS, when I try to deploy an ESS application, it shows dependency to PCUI_GP/xssutils which in turn shows dependency to PCUI_GP/xsscfg. I tried syncing and deploying PCUI_GP/cfg but it gives this error:
=> deployment aborted : file:/C:/DOCUME1/i042523/LOCALS1/Temp/temp48089sap.compcui_gpxsscfg.sda
Aborted: development component 'pcui_gp/xsscfg'/'sap.com'/'MAIN_ERP05VAL_C'/'1183085'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/pcui_gp_xsscfg.ear. Reason: None of the available containers recognized the components of application sap.com/pcui_gp~xsscfg; it is not possible to make deploy.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Could you please help here.
Thanks and regards,
Sangeeta

Hi,
Did you ever figure this out? We are having the same issue.
Thanks,
Bert

Deployment of JAVA-Patches with SUM failed, MOPZ has downloaded malicious code

some time ago, we did an upgrade of our doublestack PI-System from NW-PI-700-SPS18 to NW-PI-731-SPS05.
Now, i wanted to upgrade this PI-system from NW-PI-731-SPS05 to NW-PI-731-SPS07.
with SUM 1.0 SP10 PL4 we are now failing in the Execution-phase (Downtime):
Error in phase 5.6. execution (downtime) of the JAVA-Part
F ********************************************************************************
F *** ERROR => Node 'deployment' failed with exit code 67.
F ***
F *** Please see section 'Failures in the 'deploying offline components' phase'
F *** in SAP Note 1316652 for additional information and trouble shooting advice.
F ********************************************************************************
and the instance could not start up anymore !?
in sap-note 1316652 there is mentioned a separate sap-note 1550641 for this error
http://service.sap.com/sap/support/notes/1316652
in sap-note 1550641 - Update fails-Node 'deployment' failed with exit code 67.
http://service.sap.com/sap/support/notes/1550641
Solution:
A fix cannot be deployed as a patch, because the deployer itself is broken.
The solution is to reset a back up state of the system, to download the new version of the stack from SAP Marketplace, and to rerun the update/upgrade procedure.
i downloaded the patch-stack (with Solman MOPZ) some days ago,
so MOPZ did download the malicious code of deployment components..... ?!
so what to do?

Hi,
sorry for my late reply,
but the whole story needs a lot of time (nearly 2 month) and finally ends successfully.
first: (summary) the main-title of this thread is wrong,
it was not MOPZ or Solman download, what caused this issue.
the problem was caused by a remaining (old) sapxmltoolkit.jar in the java-bootstrap folder
details are coming ...
(all dates in yyyy-mm-dd)
=========================================
2014-05-16 at 13:04 CET:
SUM upgrade hangs with java-server did not start (in phase 5.2. Execution = downtime)
i opend OSS-ticket with several details + logs attached and opened the connection to our system.
SAP-Ticket, prio_Medium (because it is "only" a sandbox issue),
2014-05-30 at 20:21 CET:
1."sign-of-live" from sap-support,
Asking for additional logfiles from the work-directory of the sap-system
2014-06-02 at 11:14 CET:
my Answer to the questions and adding the demanded logfiles.
2014-06-02 at 21:57 CET:
2.answer from SAP-support, asking to repeat the last SUM-step, to see, if the issue is still there
2014-06-03 at 10:22 CET:
my answer after repeating SUM-step and attaching new logfiles.
2014-06-03 at 21:18 CET:
3.answer from SAP-support, i should check if system is up and running, if hostname, port-no is correct.
2014-06-03 at 10:22 CET:
my answer: hostname + portnr are o.k. - but system still did not startup (java-server)
2014-06-04 at 19:30 CET:
4.answer from SAP-support, delivering an upload-URL, could not read attached splitted .zip-files of log-files
2014-06-05 at 07:28 CET:
i did collect all logfiles again and uploaded them to the 1.upload-URL
2014-06-05 at 16:48 CET:
5.answer from SAP-support, give hint to sap-note: 1550641 - Update fails-Node 'deployment' failed with exit code 67
2014-06-06 at 10:17 CET:
i answered that (in my opinion) the mentioned sap-note did not match the issue (only to NW-7.00) ,
because i did not have to change anything, only i should do a restore from tape and start SUM from the beginning,
i insisted in more and deeper investigations by SAP-support.
2014-06-06 at 19:00 CET:
6.answer of SAP-support: moving the ticket to the next support-level (developm.support)
2014-06-09 at 10:11 CET:
7.answer from SAP-support: asking for new submittion of logfiles of work-dir.
2014-06-10 at 08:39 CET:
asking for a new upload-URL because of large logfiles
2014-06-10 at 17:31 CET:
8.answer from SAP-support: providing an new upload-URL
2014-06-10 at 17:53 CET:
i did collect all logfiles again and uploaded them to the 2.upload-URL
2014-06-12 at 09:07 CET:
9.answer from SAP-support: asking for more details, listings of directory-content of ..../j2ee/cluster/...
2014-06-12 at 10:23 CET:
i did collect all dir-infos and attached a doc to the ticket
2014-06-19 at 10:11 CET:
10.answer from SAP-support: asking for WTS-connection to start investigate and debung on our systems
2014-06-23 at 10:44 CET:
i answered, and provided WTS-connection info
2014-06-26 at 13:12 CET:
11.answer from SAP-support: could not see a running SID-engine, no SAP-MC, no directory, no folder, where is the engine?
2014-06-27 at 08:01 CET:
i answered, and provided detailed server-info and WTS-connection info,
remembering that SID is in SUM-downtime and java-server is not running, because could not be startet,
2014-06-30 at 14:01 CET:
12.answer from SAP-support: asking for an installed java6-sdk(jdk), the java6-jre is not enough to debug.
2014-07-02 at 11:40 CET:
my answer after installing java6-sdk on the WTS-server,
2014-07-07 at 15:11 CET:
13.answer from SAP-support: after debugging found an very old sapxmltoolkit.jar in the java-bootstrap folder
moving the ticket to SUM-support - java-developm-support.
2014-07-09 at 08:36 CET:
14.answer from SAP-support: (SUM-support - java-developm-support) asking for attaching the SUM stack-xml file to the ticket.
2014-07-09 at 14:32 CET:
16.answer from SAP-support: asking to remove the sapxmltoolkit.jar from the java-bootstrap folder and restart SUM (repeat last step)
2014-07-09 at 15:00 CET:
i am happy to get the solution to this issue,
after removing the .jar file from java-bootstrap folder, SUM restart last step,
the SUM-phase execution continues to run, java-server could start, ....
.... finally SUM ended successfully.
==================================
remarks:
formerly, we did a copy of that mentioned sapxmltoolkit.jar to the java-bootstrap folder (in March 2013) because of investigation PI-processes
after upgrading from NW-7.00 to NW-7.31, to get PI-system running after upgrade to NW-7.31
but maybe that formerly issues were caused by other things, cache or so ...
and since then (March 2013) we could start/stop that PI-system several times without any problem, only SUM-upgrade could not ......
i really understand that investigating problems in SAP-software (e.g. SUM-process, java-startup ...) is not easy and could have many causes.
but in summary this SUM-downtime was really large (55 days of downtime) , because of sandbox-system we want to investigate this time,
to get the solution to this issue.
if some SAP people want to look for speed-up options in the whole support-process, the OSS_ticket-no is: ( 459757 / 2014 )
Thanks to SAP-support (for the helpful solution)
Christoph

Nvidia module in X fails to load after Patch 118844-28

I'm new to Solaris so please bear with me.
I just received a shipment of Ultra 20 workstations and while setting up one of them, I used the Update manager to install all the patches. After installing the kernel update, X fails to run since the Nvidia module doesn't load, which makes sense since its a new kernel(Is this wrong, I'm used to Linux).
So I download the latest nvidia module from Nvidia.com and the installer runs with no problem. I reboot and still no go.
I've looked around and found something about using the update_drv command, and I tried that with no luck. Used reboot -- -r to reconfigure everything and still nothing. There is nothing that stands out from dmesg, so I'm at my wits end.
Any ideas?

After installing
the kernel update, X fails to run since the Nvidia
module doesn't load, which makes sense since its a
new kernel(Is this wrong, I'm used to Linux).I don't know why X or the Nvidia module fails after the kernel
upgrade...
But for Solaris is does not make sense that drivers start to fail
when the kernel is patched. This assumes the driver is using
documented kernel interfaces only - in this case a kernel update
should not cause driver failures.

After patching Portal 7.31 SP9 - SP13, CM BW reports fail

Our links to the BI credit reports (like Early Warning Risk) stopped working after patching the NW Portal 7.31 from SP9 to SP13. No other changes were made, and the reports worked prior to the patching.
The child window for the report opens, but then comes back with error:
com.sap.portal.appintegrator.sap.BWReport::BWReport/AskForReport
And then it asks for a BEx Web Application Query String.
I would put this in the portal/netweaver forum, but this error seems strictly related to the CM delivered content (we are on the most current 1.41 BP). We've validated that that the SSO tickets from portal to back end ERP and BI are working properly. Has anyone had this kind of issue after a patch (while staying on same portal release)? We didn't make any changes/patches to the back end ERP and BI systems either.

Yes we have experienced the same thing. We upgraded from 30 to 353 and now we are getting the BW logon prompt. It is very frustrating. I have been searching these message boards for help.
Brien

AIA Deployment Failed After Patching

Similar Messages

Maybe you are looking for