Odi packages with unix code

Hi Experts
I have a set of Odi Packages and want to run this code in an unix server.
Can you Please guide me in the same.
Edited by: 945367 on Jul 15, 2012 10:52 PM

Hi Sutirtha, any documents on how to install ODI agent in Unix box?
Edited by: user13599912 on Jul 19, 2012 11:48 AM
Edited by: user13599912 on Jul 19, 2012 11:49 AM
Edited by: user13599912 on Jul 19, 2012 11:49 AM

Similar Messages

Signing a package with .pfx code signing certificate

Hi,
I've got a code signing certificate (.pfx) from GlobalSign and tried to sign my extension package.
I used the ZXPSignCmd tool and got the following response:
Unable to build a valid certificate chain. Please make sure that all certificates are included in the certificate file.
The necessary certificate chain is installed on my system (Windows 7):
My code signing certificate,
the certificate from GlobalSign the signed my certificate
and the GlobalSign root certificate that signed it.
The OpenSSL info output for the certificate looks fine too:
MAC Iteration 2000
MAC verified OK
PKCS7 Data
Shrouded Keybag: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 2000
PKCS7 Encrypted data: pbeWithSHA1And40BitRC2-CBC, Iteration 2000
Certificate bag
Certificate bag
Certificate bag
On the other hand signing other files with the Windows SDK Signtool works and results in a correct certificate chain (visible in the file's details).
Any idea what I might be doing wrong?
Regards
Philipp

Hi Philipp,
No, it doesn't matter - using Certificate Manager should also have worked.
I don't think the issue is that the wrong root certificate has been chosen, otherwise we'd be seeing a different error. In the PEM file you exported, I would expect to see several certificate sections, each starting with BEGIN CERTIFICATE and ending with END CERTIFICATE. Just above each certificate's "BEGIN CERTIFICATE" line should be "subject" and "issuer" - the last certificate (at the bottom of the PEM file), should have your personal certificate name as the subject. Then, working upwards, each certificate should have an "issuer" which matches the "subject" of the certificate above it.
The first certificate in the PEM file should have the same value for "subject" and "issuer" - identifying the certificate authority's root certificate.
Also in the PEM file I'd expect to see a section "BEGIN RSA PRIVATE KEY"...."END RSA PRIVATE KEY".
Does this all match what you're seeing?
Assuming your PEM file looks OK, you could try using OpenSSL to convert it to PKCS12 format, using the command:
openssl pkcs12 –export –in my_pem_file.pem –out my_pkcs12_file.p12
Also, please ensure that you're using only ASCII characters in your P12 password, just in case that's causing problems.
Best regards,
Fraser

ODI Package + Calling via Unix wrapper

Hi,
I am new to ODI... Can you please help me on this.
On Overall architecture we are 3 products
1. ODI for staging to target transformaton
2. AbInitio conduct>IT for dependency analyisis and as work flow ( It can call Unix scripts, programs, SQL etc)
3. dServies a scheduling product ( Which will schedule the Conduct>IT workflow)
My question is can we wrapper the ODI Packages in UNIX and pass on the parameters? ( What i want to achieve is i want to put these wrappers in AbInitio workflow product).
Can you please share with me any sample Unix script calling the ODI Packages via Unix wrappers; if we can do it?
Many thanks

Hi,
Check this out
http://www.oracle.com/technology/products/oracle-data-integrator/10.1.3/htdocs/documentation/oracledi_getting_started.pdf
http://www.oracle.com/technology/products/oracle-data-integrator/10.1.3/htdocs/documentation/oracledi_users.pdf
http://www.oracle.com/technology/obe/fusion_middleware/ODI/index.html
Thanks,
Sutirtha

ERROR: DW006: Apple Package failed to install successfully. ERROR: Third party payload installer Adobe Photoshop Lightroom 5.pkg failed with exit code: 1

Hi,
i have the following message when i tried to install LR 5.6
Exit Code: 7
Please see specific errors below for troubleshooting. For example, ERROR: DW006 ...
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 2 error(s)
----------- Payload: Adobe Photoshop Lightroom 5 5.6.0.0 Adobe Photoshop Lightroom 5.pkg_5.6 -----------
ERROR: DW006: Apple Package failed to install successfully.
ERROR: Third party payload installer Adobe Photoshop Lightroom 5.pkg failed with exit code: 1
how can i solve this issue?
I am running on Mac with OSX 10.9.4
thanks in advance
Olivier

olebreth wrote:
how can i solve this issue?
A search of the site would probably be a good start:
https://forums.adobe.com/search.jspa?q=dw006

ERROR: DW006: Apple Package failed to install successfully. ERROR: Third party payload installer Adobe Acrobat XI Pro Installer.pkg failed with exit code: 1

Hi All, anyone with this problem with Acrobat Pro XI, IM USING MAC, also Yosemite if that helps.
Also Adobe CC, BASICALLY IT just quit and i had to uninstall, re install, and I get this
ERROR: DW006: Apple Package failed to install successfully.
ERROR: Third party payload installer Adobe Acrobat XI Pro Installer.pkg failed with exit code: 1
Anyone with same issues...

Same problem. Creative Cloud subscriber running Mac 10.10.2 on iMac (Retina 5K, 27-inch, Late 2014). All apps work fine EXCEPT for Adobe Acrobat XI. I have tried 100 times and 100 solutions. NOTHING works.

I just purchased a camera packaged with Adobe photoshop Elements 11. I have a mac book air- which does not have a cd drive. The package did not come with a code or anything that would provide me with another way to install photoshop that came with my came

I just purchased a camera packaged with Adobe photoshop Elements 11. I have a mac book air- which does not have a cd drive. The package did not come with a code or anything that would provide me with another way to install photoshop that came with my camera. Is there any other way i can install this on my camera without using the provided cd or buying the software again?

That doesn't help the user with the serial code though.
There has to be some kind of code somewhere within the package. The disk itself does not contain one. You can look here for help with finding your serial number:
Find your serial number quickly

ODI-1217 session fails with return code 904

Hi all,
I am anil, I new to ODI, can any one help me in it.
I have just created a one on one mapping, and then executed it, and I am getting "ODI-1217 session fails with return code 904" this error, what to do, why it happens, can any have any idea.
Thanks,
Anil

Hi,
it just returns this error.Could you copy here all error ?
Regards

Basic Package Deployment - Failed with exit code 1

Hello everyone!
I am new to SCCM and I am trying to create my first package and it is a basic one (I suppose).
What I am trying to do is to install the File & Printer Sharing service on all Windows 7 computers in our domain. It is completely uninstalled (not only uncheck from the network adapter properties).
I created a .cmd with these two lines
cmd /c
netcfg /c s /i MS_Server
I create the package/program and configure it to download and run locally. I always get this error in execmgr : Script for Package:ALI00022, Program: File & Printer Sharing - Installation failed with exit code 1 execmgr 10/5/2014 5:55:43 PM 1712
(0x06B0)
I can see the package has been downloaded in the folder c:\windows\ccmcache\ of the client machine.
When I launch the file there by running it as Administrator, it does work perfectly.
When I launch the file by opening a command prompt (not running as administrator) it is not working. I am now supposing that the main problem I have is when my script need to be run as an administrator, it doesn't work.
Thank you for your help!

Ok,
I used psexec to run the script in the SYSTEM context and it is working correctly.
I tried to recreate a package in SCCM by using the command line only.
here is what I got in my execmgr.log
Successfully prepared command line "C:\Windows\system32\netcfg.exe" /c s /i MS_Server execmgr 10/6/2014 12:21:34 PM 3484 (0x0D9C)
Command line = "C:\Windows\system32\netcfg.exe" /c s /i MS_Server, Working Directory = C:\Windows\system32\ execmgr 10/6/2014 12:21:34 PM 3484 (0x0D9C)
Running "C:\Windows\system32\netcfg.exe" /c s /i MS_Server with 32bitLauncher execmgr 10/6/2014 12:21:34 PM 3484 (0x0D9C)
CreateProcess or CreateProcessAsUser failed to execute command line with non-recoverable error 0x80070002 execmgr 10/6/2014 12:21:41 PM 3484 (0x0D9C)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramUnableToExecuteEvent
AdvertisementId = "ALI2000D";
ClientID = "GUID:D357F21F-E804-41AB-AB39-4B874C635118";
CommandLine = "\"C:\\Windows\\system32\\netcfg.exe\" /c s /i MS_Server";
DateTime = "20141006162141.138000+000";
MachineName = "L1WIN7";
PackageName = "ALI00023";
ProcessID = 1940;
ProgramName = "File & Printer Sharing - Installation";
SiteCode = "ALI";
ThreadID = 3484;
Win32ErrorCode = 2147942402;
WorkingDirectory = "C:\\Windows\\system32\\";
execmgr 10/6/2014 12:21:41 PM 3484 (0x0D9C)
Raised Program Unable to Execute Event for Ad:ALI2000D, Package:ALI00023, Program: File & Printer Sharing - Installation execmgr 10/6/2014 12:21:41 PM 3484 (0x0D9C)
EnterRsRuningState failed to run script netcfg /c s /i MS_Server 0x87d01101 execmgr 10/6/2014 12:21:41 PM 3484 (0x0D9C)
Fatal error 0x87d01101 enountered for program File & Printer Sharing - Installation. This program will not retry. execmgr 10/6/2014 12:21:42 PM 3484 (0x0D9C)

Problem with Reports Server and invalid DB packages when release code

Hello,
I'm not certain that this is a Reports issue or not, but wondered if anyone had encountered similar. We've recently upgraded from Forms and Reports 6i to 10.1.2.0.2. A couple of times now, after doing a release of code to our environment, we find that the next request to the Reports Server generates a 'existing state of packages has been discarded' error. Submitting exactly the same report request a second and subsequent times works fine.
However, we always make sure we recompile all invalid packages after a code release; and our Forms front-end doesn't encounter any errors like this. Is there some possible issue with using existing Reports engines to run reports after a code release - should we be bouncing the Reports server..?
Thanks,
James

Hi. Thanks for your quick response. The contain of StrSql is:
"SELECT IdTipo FROM TIPOSTELEFONO", where IdTipo id a column of TIPOSTELEFONO Table.
I tryied the same sql setence with SQL Server Management Studio Express and it works fine. Already I have tryied with others sql sentences. All they worked fine in SQL Server Management Studio, but not with my java example using sqljdbc4.jar.
sqljdbc4.jar documentation comment that these driver work with sql server 2000 to sql server 2008. I'll ask this cuestion in Microsoft forums.
Thanks.

ODI Session task reverse fails with return code 7000

WARNING ODI-1134 Agent Test encountered an error: ODI-12: Step Hyperion Planning ODI fails after 1 attempt(s).
2013-10-28 16:14:38.471 ERROR ODI-1217 Session Hyperion Planning ODI (23121) fai
ls with return code 7000.in the Command prompt
Target Code in session task reverse
from java.util import HashMap
from java.lang import Boolean
from com.hyperion.odi.common import ODIConstants
from com.hyperion.odi.common import ODIModelImporter
from com.hyperion.odi.connection import HypAppConnectionFactory
# source planning connection properties
serverName = "192.168.0.105:19000"
userName = ""
password = "<@=snpRef.getInfo("SRC_PASS") @>"
application = "FirstApp"
srvportParts = serverName.split(':',2)
srvStr = srvportParts[0]
portStr = srvportParts[1]
# Put the connection properites and initialize the planning loader
srcProps = HashMap()
srcProps.put(ODIConstants.SERVER,srvStr)
srcProps.put(ODIConstants.PORT,portStr)
srcProps.put(ODIConstants.USER,userName)
srcProps.put(ODIConstants.PASSWORD,password)
srcProps.put(ODIConstants.APPLICATION_NAME,application)
imod = 4121
#get planning connection
hApp = HypAppConnectionFactory.getAppConnection(HypAppConnectionFactory.APP_PLANNING, srcProps);
#get connection to repository
repCon = odiRef.getJDBCConnection("DEST")
# START THE REVERSE
odiModelImporter = ODIModelImporter(imod, hApp, repCon)
odiModelImporter.importModels()

yes , I have entered all the details in the Topology for Planning Data server, [ since it is Hyperion Planning the test connection is disable]
The created agent test connection also successfull But still it is not connecting .GEtting the
Error :-
2013-10-29 10:14:52.151 NOTIFICATION ODI-1137 Scheduler started for work reposit
ory WORKREP121 on Agent Test.
2013-10-29 10:15:35.664 WARNING ODI-1134 Agent Test encountered an error: ODI-12
26: Step Hyperion Planning ODI fails after 1 attempt(s).
2013-10-29 10:15:35.665 ERROR ODI-1217 Session Hyperion Planning ODI (24121) fai
ls with return code 7000

ODI Error: ODI-1217: Session jobname (2197102) fails with return code 700

Hi All,
We are getting the below error when running an interface in our ODI 11.1.6 environment.
ODI-1217: Session <interfacename> (2197102) fails with return code 7000.
Caused By: com.sunopsis.tools.core.exception.SnpsSimpleMessageException: ODI-17517: Error during task interpretation.
Task: 147
java.lang.Exception: BeanShell script error: Parse error at line 26, column 38. Encountered: >= BSF info: Insert flow into I$ table at line: 0 column: columnNo
at com.sunopsis.dwg.codeinterpretor.SnpCodeInterpretor.transform(SnpCodeInterpretor.java:485)
at com.sunopsis.dwg.dbobj.SnpSessStep.createTaskLogs(SnpSessStep.java:711)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:461)
The interface is a simple pass-through one which loads data from one table to another. We have checked in the interface for any discrepancies but could not find any issue. We ran the same interface in another environment and it ran fine there. Restarting the agent also didnt help. We could not find any lead for any solutions. Any help on the issue would be highly appreciated.
P.S: Interface name has been kept generic to <jobname>
Thanks,
Shrinivas

Please give the code generated in that step ( Insert flow into I$ table.)

ODI-1217: (6003) fails with return code 7000.

Hi
I'm learning ODI. I got stuck while i execute the interface - i get that error message --> ODI-1217: Session test1_load_data_from_and_to_oracle (6003) fails with return code 7000.
My source, staging area, Target all are in oracle DB.
I believe the reason is that I do not choose the right IKM. but i export and execute all ikm type for oracle.
I would appreciate your help.
ODI-1217: Session test1_load_data_from_and_to_oracle (6003) fails with return code 7000.
ODI-1226: Step test1_load_data_from_and_to_oracle fails after 1 attempt(s).
ODI-1240: Flow test1_load_data_from_and_to_oracle fails while performing a Integration operation. This flow loads target table TRG_COUNTRIES.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 1, in ?
Defining a target, but no source has been defined, yet. Please define source first.
 at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
 at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:345)
 at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:169)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2374)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1615)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1580)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java:2755)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java:68)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2515)
 at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:534)
 at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:449)
 at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1954)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:322)
 at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:224)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:246)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:237)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:794)
 at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:114)
 at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
 at java.lang.Thread.run(Thread.java:619)

hi,
When I chose--> IKM sql control append--> it worked .
Where can I find the types of KM processes and explain how to use them?
Thanks in advance

Calling UNIX shell script from ODI package?

Hi,
How Can we call UNIX shell script from ODI package?
I have a ftp_ss.sh script which which ftps a file from remote server to local server, archives the last file and renames new file to the standard (ie file data store)name.
I want to run the above script and interfaces from a package.
Any help is greately appreciated.
Thanks,
RD

In the package window, put "OS Command" from the toolbox.
Provide the command parameters to this tool in form of "/path/to/script/ftp_ss.sh"

-Support package-Test import---Ended with return code: === 8 ===(Urgent)

Dear all, using -
> SAP ECC 6.0 with IS - AFS 6.0
Environment -- Win2k3 with Orc 10.2
Kernel 700 - 75
Spam/Saint - 70026
R3trans -d <0000>
STMS is very consistent.
Met all the pre-requisites when applying Support packs & going succesfull
but
While applying
Sapk-60004inafs CRT with sapkh 60009,10,11 in
Test_import phase it is showing the following error for
sapkh 60010.
Test import
Transport request : SAPKH60010
System : MBD
tp path : tp
Version and release: 370.00.09 700
R3TRPROGJ_1IRUTZN was repaired in this system
R3TRPROGJ_1IRUTZN was repaired in this system
Test import
End date and time : 20080410100230
Ended with return code: ===> 8 <===
When im runing with 700-75 is it possoble to import latest TP
<SAR tp_145-20001354.sar TP 145 Info 3317 30.01.2008 >
in to existing kernel. plaese coment on this as i think it's a TP error.
please also advice me in different areas.
Cheers,
Rahul

HI thanx a lot ,
It the same procedure i did & checked your message indicating the same steps .
Yes ,standard object is repaired in system & im not aware of that
& even it is not shown that it is recorded to work bench change request when i started applying the support pack.
I did the same went to SE03 selected the object .
Selected lock overview
Identified the change request & released it.
I got one more doubt what happens when i set the object to repair flag.
Cheers ,
Rahul

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Odi packages with unix code

Similar Messages

Maybe you are looking for