ODI Agent after Restarting/Rebooting Server

Hi All,
How can ODI Agent executes after we Restart/Reboot our Servers?
Thanks,
Randy

If you are using Windows machine then you can set up ODI Agents as Windows Services .
Metalink Note 423712.1 can be helpful in this case .
Once the ODI Agents is running as Windows Services , you can specify the service startup type as Automatic.
So when your windows server gets restarted , ODI agent service will also start.
If you are using Unix based system then create a script that contains the agent.sh/agentscheduler.sh
Specify all required parameter .
Then get in touch with your system admin and place the script inside the folder
which contains all the start-up scripts .

Similar Messages

Site does not load after some minutes of creation or after restart the server

Hello,
I have been asked to create a test enviroment identical to the production enviroment. So, what I did was:
Backed up the production web application's content database: Prod_WSS_ContentDB
Created new test servers (domain controller, sql server and sharepoint 2013 server) in a new, completely isolated, network environment, without any connection with the production environment (specifically Azure)
Created a new web application in test environment with a new content database.
Dismounted the new content database with powershell: Dismount-spcontentdatabase Test_WSS_Content
Copy the Prod_WSS_ContentDB database to the test sql server and restored it with Management Studio.
Mount the Prod_WSS_ContentDB databe to the web application with powershell:
Mount-spcontentdatabse Prod_WSS_ContentDB -WebApplication http://testsp/
Then, when I type http://testsp in the browser it redirects me to http://testsp/SitePages/Home.aspx
and the site loads exactly as the production environment.
But, after some minutes, or if I restart the Sharepoint Server, when I navigate to
http://sitesp I am redirected to http://testsp/SitePages/Home.aspx
as expected, but the site does not load, the browser just show a complety blank page.
The Central Administration site loads normally.
Trying to fix it I found that if I dismount the content database Prod_WSS_ContentDB, then mount the test database Test_WSS_Content,
then navigate to the site, dismount Test_WSS_Content and finally mount again Prod_WSS_ContentDB, the site loads normally, no blank page, but after some minutes or if I restart the same happens again.
For the error event I receice in event viewer it seems that the problem is related to database. I have not found a solution for this error... How can I solve this?
The error is:
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation
Date: 6/27/2014 2:44:22 PM
Event ID: 5586
Task Category: Database
Level: Error
Keywords:
User: UCETEST\spaccount
Computer: TESTSP01.ucetest.edu.do
Description:
Unknown SQL Exception -2146893055 occurred. Additional error information from SQL Server is included below.
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The handle specified is invalid)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
<EventID>5586</EventID>
<Version>15</Version>
<Level>2</Level>
<Task>3</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-06-27T14:44:22.743159500Z" />
<EventRecordID>4742</EventRecordID>
<Correlation />
<Execution ProcessID="1688" ThreadID="1692" />
<Channel>Application</Channel>
<Computer>TESTSP01.ucetest.edu.do</Computer>
<Security UserID="S-1-5-21-2552298216-324766354-3392103171-1108" />
</System>
<EventData>
<Data Name="int0">-2146893055</Data>
<Data Name="string1">A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The handle specified is invalid)</Data>
</EventData>
</Event>
Melvintt
MCTS, Windows Server 2008 R2: Network Infrastructure
MCTS, Windows Server 2008 R2: Active Directory, Configuring

Hi,
According to your post, my understanding is that Site does not load after some minutes of creation or after restart the server.
Please make sure you create a test environment for existing production site correctly.
Here are some great articles for your reference:
Moving content between SharePoint environments
Copy SharePoint production data to a test environment
Build a SharePoint 2010 Test/Development Farm
Best Regards,
Linda Li
Linda Li
TechNet Community Support
Hello Linda Li,
I follwed that steps to create my test enviroment... and I have recreated it some times using that same steps, but the problem persits. After some minutes or after I restart the SharePoint server the site does not load.
Melvintt
MCTS, Windows Server 2008 R2: Network Infrastructure
MCTS, Windows Server 2008 R2: Active Directory, Configuring

Running Multiple ODI Agents On The Same Server

Is it possible to run multiple ODI Scheduler Agents simultaneously on the same Server?
As we provide Work repository name in ODI params file and if we have different work repository
and we want to run schedular agent on same server how can we point to the other work repository.
Do we need to create another installation of ODI agent files on same server?
Thanks
Kashi

Hey Kashi,
You do not have to instal a separate Agent files again. All you need to do is to make sure that each set of agent has all the required parameter files which inclues, odiparams.bat , agentstart.bat and agentstop.bat(names may not be exactly same). Here is a website that gives you more details regarding creating multiple agents on same server
http://www.business-intelligence-quotient.com/?tag=odi-agents
regards,
k

Linked Server unable to Connect in SQL Server 2012 after Restarting SQL Server Service it works fine. Why?

I have created a Linked Server to Access Database of 64 MB in Size located in Remote System to SQL Server 2012.In Start for Some time it works fine and after it is giving the Error
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
Previously I thought it as Permission Issue. By trying some fixes proposed in forums it not fixed. But, after restarting the SQL Server Services without changes to the linked Server it works perfectly. How could i fix it. I don't want restart the SQL Server
Service it leads to Some other process failures.
RehaanKhan. M

After all the Errors, When I am restarting the SQL Server its working correctly.
Whats the problem it is clearing itself after restarting of SQL Server. Why ?. I can't find anything regarding this in SQL Server .
The following are the Errors i got connecting to SQl Server.
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
Error-2:
Executed as user: RMS\Administrator. Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST". [SQLSTATE 42000] (Error 7303) OLE DB provider
"Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.". [SQLSTATE 01000] (Error 7412). The step failed.
After unchecking the Allow In Process in OLEDB.ACE Provider Properties.
Msg 7399, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
The OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" reported an error. Access denied.
Msg 7301, Level 16, State 2, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
for to fix above error i have followed the instructions in the following link,
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider.aspx
This also failed to work. I Restarted SQL Server and make the Linked Server Properties Default to my Configuration and it works fine.
Can you suggest me a solution for this issue. Every time i don't want to restart SQL Server Services as it effects other jobs and Processes.
Thank you.
RehaanKhan. M

Saving chart data and reload after restart of server?

Hi
I have a vi that communicate with another program called EES through DDE and sometimes EES mess up the server. My solution is to automatically restart the server once a day [this is good enough for me].
My question is: How do I get all my data in my charts to save and reload easiest?

Hi,
I think you may create a database table in your server and then pass your data to this table every time a new entry is made and calling the same from the database every time you run the VI after its restart. This can easily be done using the database connectivity tool-kit in the function palette.
Regards,
Nitz.
(Kudos are always welcome)

Instances In recovery are getting recovered only after restart of server.

Hi All,
The issue I face is :There is a BPEL Process with a DB adapter which has to poll on a database.
Now my DB adapter polls,but the instance in EM remains in Recovery State.
From BPEL Service Engine even if I recover,they dont get recovered.
But,If I restart the server(SOA) and and From BPEL Service Engine if I recover,they get recovered.
SO,every Time I hav to restart the server.:-( :-(
Kindly ,suggest the solution.

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

Need help!---lookup connectionFactory failed after restart j2ee server!

hi,
I wonder anyone could help me to solve this context lookup problem described as bellows.i should say 'thanks' in advance!!!
At the end of the message i post the code used to lookup administered objects then create connection.
i use sun's default jms implementation (j2sdkee1.3.1) and jdk1.4 as environment.
The jms client will try to establish a new connection if the j2ee server restarts (perhaps due to remote j2ee server shutdown or network trouble) , but it fails to lookup topicConnectionFactory in the JNDI this time. An namingException will be caught :
"javax.naming.CommunicationException: java.rmi.MarshalException: CORBA COMM_FAILURE 1398079689 No; nested exception is:
     org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
     at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.mapSystemException(ShutdownUtilDelegate.java:92)
     at javax.rmi.CORBA.Util.mapSystemException(Util.java:65)
     at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.lookup(Unknown Source)
     at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:120)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
     at com.sun.corba.ee.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:176)
     at com.sun.corba.ee.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:68)
     at com.sun.corba.ee.internal.iiop.GIOPImpl.getConnection(GIOPImpl.java:70)
     at com.sun.corba.ee.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:641)
     at com.sun.corba.ee.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:583)
     at com.sun.corba.ee.internal.corba.ClientDelegate.request(ClientDelegate.java:875)
     at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:431)
     at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.lookup(Unknown Source)
     ... 6 more
Some code in the establish() method:
try {
TopicConnectionFactory topicConnectionFactory = null;
InitialContext ctx = null;
ctx = new InitialContext();
System.out.println("ctx:" + ctx);
topicConnectionFactory =
(TopicConnectionFactory) ctx.lookup ("connectionfactory");
System.out.println("topicConnectionFactory:" + topicConnectionFactory);
while (connection == null)
try{
connection = topicConnectionFactory.createTopicConnection();
} catch (javax.jms.JMSException jmse)
System.out.print("Cannot connect to message server...");
System.out.println("Pausing " +
CONNECTION_RETRY_PERIOD / 1000 + " seconds before retry.");
try
Thread.sleep(CONNECTION_RETRY_PERIOD);
} catch (java.lang.InterruptedException ie) {ie.printStackTrace();}
continue;
System.out.println("\nConnection established");
session =
connection.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
topic = (Topic) ctx.lookup ("subscribeTopic");
connection.setExceptionListener( (javax.jms.ExceptionListener) this);
catch (javax.naming.NamingException jne){
System.err.println("[MessageSubscriber] - NamingException!");
//jne.printStackTrace( );
Best Regards,
-bawanglongqiqi

Hi!
I've encountered a similar problem with looking up the Home-interface
of an EJB from a client through the InitialContext object after a
restart of the application server.
Try to set an additional property before creating your InitialContext
object that clears the JNDI cache (the property name seems to differ
between context factories - e.g. I'm using a WebSphere one and had to
set a WebSphere specific property name).
I'm sure you will find further info when you do a web search on "clear
JNDI cache" for your specific JNDI provider.
Kind regards,
Markus

Happenning non regurarly and will be ok after restarting the server again.

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6c3e0f3c Function name=Ordinal6467 Library=C:\WINNT\system32\MFC42.DLL
Current Java thread:
at
com.ag.id.comwrapper.server.COMServer.NativeGetTermPremiums(Native Method)
at
com.ag.id.comwrapper.server.COMServer.getTermPremiums(COMServer.java:89)
at java.lang.reflect.Method.invoke(Native Method)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.lang.Thread.run(Unknown Source)
Dynamic libraries:
0x00400000 - 0x00405000 C:\WINNT\system32\java.exe
0x77F80000 - 0x77FFD000 C:\WINNT\system32\ntdll.dll
0x7C2D0000 - 0x7C332000 C:\WINNT\system32\ADVAPI32.dll
0x7C570000 - 0x7C624000 C:\WINNT\system32\KERNEL32.DLL
0x77D30000 - 0x77D9F000 C:\WINNT\system32\RPCRT4.DLL
0x78000000 - 0x78045000 C:\WINNT\system32\MSVCRT.dll
0x6D420000 - 0x6D4F9000 C:\Program Files\JavaSoft\JRE\1.3.1
_06\bin\hotspot\jvm.dll
0x77E10000 - 0x77E6F000 C:\WINNT\system32\USER32.dll
0x77F40000 - 0x77F7C000 C:\WINNT\system32\GDI32.dll
0x77570000 - 0x775A0000 C:\WINNT\system32\WINMM.dll
0x6D220000 - 0x6D227000 C:\Program Files\JavaSoft\JRE\1.3.1
_06\bin\hpi.dll
0x6D3B0000 - 0x6D3BD000 C:\Program Files\JavaSoft\JRE\1.3.1
_06\bin\verify.dll
0x6D250000 - 0x6D266000 C:\Program Files\JavaSoft\JRE\1.3.1
_06\bin\java.dll
0x6D3C0000 - 0x6D3CD000 C:\Program Files\JavaSoft\JRE\1.3.1
_06\bin\zip.dll
0x24F10000 - 0x24F28000 C:\COMServer\SpiaWrapper.dll
0x7C140000 - 0x7C243000 C:\WINNT\system32\MFC71.DLL
0x7C340000 - 0x7C396000 C:\WINNT\system32\MSVCR71.dll
0x70A70000 - 0x70AD6000 C:\WINNT\system32\SHLWAPI.dll
0x7CE20000 - 0x7CF0F000 C:\WINNT\system32\ole32.dll
0x779B0000 - 0x77A4B000 C:\WINNT\system32\OLEAUT32.dll
0x7C950000 - 0x7C9DF000 C:\WINNT\system32\CLBCATQ.DLL
0x253D0000 - 0x25467000 C:\COE64A~1\COMDLLs\CLIENT~1.DLL
0x6C370000 - 0x6C46B000 C:\WINNT\system32\MFC42.DLL
0x780A0000 - 0x780B2000 C:\WINNT\system32\MSVCIRT.dll
0x25470000 - 0x2568B000 C:\COE64A~1\COMDLLs\PRODUC~1.DLL
0x76B30000 - 0x76B6E000 C:\WINNT\system32\comdlg32.dll
0x71710000 - 0x71794000 C:\WINNT\system32\COMCTL32.DLL
0x7CF30000 - 0x7D176000 C:\WINNT\system32\SHELL32.DLL
0x77800000 - 0x7781E000 C:\WINNT\system32\WINSPOOL.DRV
0x76620000 - 0x76630000 C:\WINNT\system32\MPR.DLL
0x257A0000 - 0x257E2000 C:\COE64A~1\COMDLLs\RETURN~1.DLL
0x257F0000 - 0x25818000 C:\COE64A~1\COMDLLs\VALIDA~1.DLL
0x25820000 - 0x2584E000 C:\COE64A~1\COMDLLs\Annuity.dll
0x26060000 - 0x26071000 C:\COMServer\COMWrapper.dll
0x260C0000 - 0x260F2000 C:\COE64A~1\COMDLLs\TrmCalc.dll
0x261A0000 - 0x261AE000 C:\COE64A~1\COMDLLs\TERMCH~1.DLL
0x6D340000 - 0x6D348000 C:\Program Files\JavaSoft\JRE\1.3.1
_06\bin\net.dll
0x75050000 - 0x75058000 C:\WINNT\system32\WSOCK32.dll
0x75030000 - 0x75044000 C:\WINNT\system32\WS2_32.DLL
0x75020000 - 0x75028000 C:\WINNT\system32\WS2HELP.DLL
0x782C0000 - 0x782CC000 C:\WINNT\System32\rnr20.dll
0x77980000 - 0x779A4000 C:\WINNT\system32\DNSAPI.DLL
0x77340000 - 0x77353000 C:\WINNT\system32\iphlpapi.dll
0x77520000 - 0x77525000 C:\WINNT\system32\ICMP.dll
0x77320000 - 0x77337000 C:\WINNT\system32\MPRAPI.dll
0x75150000 - 0x7515F000 C:\WINNT\system32\SAMLIB.DLL
0x7CDC0000 - 0x7CE10000 C:\WINNT\system32\NETAPI32.DLL
0x267D0000 - 0x267DF000 C:\WINNT\system32\Secur32.dll
0x77BF0000 - 0x77C01000 C:\WINNT\system32\NTDSAPI.dll
0x77950000 - 0x7797A000 C:\WINNT\system32\WLDAP32.DLL
0x751C0000 - 0x751C6000 C:\WINNT\system32\NETRAP.dll
0x773B0000 - 0x773DF000 C:\WINNT\system32\ACTIVEDS.DLL
0x77380000 - 0x773A3000 C:\WINNT\system32\ADSLDPC.DLL
0x77830000 - 0x7783E000 C:\WINNT\system32\RTUTILS.DLL
0x77880000 - 0x7790E000 C:\WINNT\system32\SETUPAPI.DLL
0x267E0000 - 0x26841000 C:\WINNT\system32\USERENV.DLL
0x774E0000 - 0x77513000 C:\WINNT\system32\RASAPI32.dll
0x774C0000 - 0x774D1000 C:\WINNT\system32\RASMAN.DLL
0x77530000 - 0x77552000 C:\WINNT\system32\TAPI32.DLL
0x77360000 - 0x77379000 C:\WINNT\system32\DHCPCSVC.DLL
0x777E0000 - 0x777E8000 C:\WINNT\System32\winrnr.dll
0x777F0000 - 0x777F5000 C:\WINNT\system32\rasadhlp.dll
0x74FD0000 - 0x74FEE000 C:\WINNT\system32\msafd.dll
0x75010000 - 0x75017000 C:\WINNT\System32\wshtcpip.dll
0x26BF0000 - 0x26C20000 C:\COE64A~1\COMDLLs\ADOFUN~1.DLL
0x26C20000 - 0x26C9C000 C:\Program Files\Common
Files\System\ADO\msado15.dll
0x26CA0000 - 0x26CC4000 C:\WINNT\system32\MSDART.DLL
0x77820000 - 0x77827000 C:\WINNT\system32\VERSION.dll
0x759B0000 - 0x759B6000 C:\WINNT\system32\LZ32.DLL
0x26F50000 - 0x26FBC000 C:\Program Files\Common Files\System\OLE
DB\oledb32.dll
0x26FC0000 - 0x26FD1000 C:\Program Files\Common Files\System\OLE
DB\OLEDB32R.DLL
0x26FE0000 - 0x2702A000 C:\Program Files\Common Files\System\OLE
DB\msdasql.dll
0x27030000 - 0x27045000 C:\Program Files\Common Files\System\OLE
DB\MSDATL3.dll
0x27050000 - 0x27086000 C:\WINNT\system32\ODBC32.dll
0x271D0000 - 0x271E7000 C:\WINNT\system32\odbcint.dll
0x271F0000 - 0x271F4000 C:\Program Files\Common Files\System\OLE
DB\MSDASQLR.DLL
0x78740000 - 0x788B0000 C:\WINNT\System32\comsvcs.dll
0x6DE80000 - 0x6DEE4000 C:\WINNT\System32\TxfAux.Dll
0x6DF80000 - 0x6E03B000 C:\WINNT\System32\MSDTCPRX.dll
0x6A7A0000 - 0x6A7B0000 C:\WINNT\System32\MTXCLU.DLL
0x73930000 - 0x73940000 C:\WINNT\system32\CLUSAPI.DLL
0x689D0000 - 0x689DD000 C:\WINNT\system32\RESUTILS.DLL
0x272C0000 - 0x27302000 C:\WINNT\System32\odbcjt32.dll
0x27310000 - 0x27480000 C:\WINNT\System32\msjet40.dll
0x27480000 - 0x27515000 C:\WINNT\System32\mswstr10.dll
0x27D40000 - 0x27D4E000 C:\WINNT\System32\odbcji32.dll
0x27D50000 - 0x27D5D000 C:\WINNT\System32\msjter40.dll
0x27D60000 - 0x27D86000 C:\WINNT\System32\MSJINT40.DLL
0x281A0000 - 0x281BA000 C:\WINNT\system32\odbccp32.dll
0x308E0000 - 0x3091A000 C:\WINNT\System32\msjtes40.dll
0x30D30000 - 0x30D3B000 C:\WINNT\system32\VBAJET32.DLL
0x31150000 - 0x311B2000 C:\WINNT\system32\expsrv.dll
0x31940000 - 0x3194D000 C:\Program Files\Common
Files\System\ADO\msadrh15.dll
0x2C480000 - 0x2C4CC000 C:\WINNT\System32\msrd3x40.dll
0x77920000 - 0x77943000 C:\WINNT\system32\imagehlp.dll
0x72A00000 - 0x72A2D000 C:\WINNT\system32\DBGHELP.dll
0x690A0000 - 0x690AB000 C:\WINNT\system32\PSAPI.DLL
Local Time = Wed Sep 19 17:21:38 2007
Elapsed Time = 452155
# The exception above was detected in native code outside the VM # # Java VM: Java HotSpot(TM) Client VM (1.3.1_06-b01 mixed mode)

Hi,
I'm not sure if you damaged your sqlnet.ora and listener.ora files after the server was up. So, I would try make some tests:
1) Rename the listener.ora file to listener.ora.bak and sqlnet.ora file to sqlnset.ora.bak
2) Restart the listener and see what happens
Cheers
Legatti

After restarting server BI Publisher is not started automatically

Hi all,
I am new in BI Publisher and have a problem. When I installed BI everything works OK. So I have logged on Publisher URL, authentication was successful and etc.
After restarting the server (I have Oracle DB and Publisher in one server, but in different home) I tried to log on to the Publisher console (http://oraclebi.mycompany.ge:9704/xmlpserver) and url is not responding,seems that service is not started.
Configurationdetails:
Installation Details
Middleware Home: /u01/app/oracle/bi
BI Oracle Home: /u01/app/oracle/bi/Oracle_BI1
WebLogic Server Home: /u01/app/oracle/bi/wlserver_10.3
BI Domain Home: /u01/app/oracle/bi/user_projects/domains/bifoundation_domain
BI Domain Name: bifoundation_domain
Instance Home: /u01/app/oracle/bi/instances/instance1
Instance Name: instance1
Configure Components
WebLogic Console
http://oraclebi.mycompany.ge:7001/console
Oracle Enterprise Manager
http://oraclebi.mycompany.ge:7001/em
Business Intelligence Enterprise Edition
http://oraclebi.mycompany.ge:9704/analytics
Business Intelligence Publisher
http://oraclebi.mycompany.ge:9704/xmlpserver
Could anyone help me how to start this service or how to setup to start it automatically?
Thank in advance
Edited by: zmachavariani on 17.01.2011 2:27

Hi,
There are many version of BI Publisher and also it can be deployed in many app servers. But from your log messages
I can see you are trying to use BIP 11g in Weblogic Server (besides 11g only allows -as of today- to install in WLS).
You should be aware that BIP11g after default installation uses a repository which is part of the BIEE Catalog and also
uses FUSION as security Mode (i.e. users and pwds are no longer controled in BIEE Admin but in OEM).
Therefore for BIP11g to work as default installation you also need BIEE11g to be running. For this i recommend you
to first take a look at one of my posts:
http://oraclebiblog.blogspot.com/2010/10/obiee-11g-architecture.html
and then follow the guidelines to start it all:
http://oraclebiblog.blogspot.com/2010/11/starting-and-stopping-biee-from-command.html
Now, if you only want to use BIP11g there is a workaround. Make a backup of xmlp-server-config.xml
and update the SECURITY mode from FUSION to XDO. Set a Local user for BIP and
Restart BIP11g from within OEM and login as Local User.
regards
Jorge A.

Trace flow is stoped in timer event after reboot server

Hi friends
I have a flow where there are three elements:
The first one is a service task that looks for an event in a database using a database adapter
The second is a gateway, if the event was found, the flow continues otherwise the flow goes to a timer event
Timer event waits for 10 minutes and, after that, returns to the first element (the service task).
The flow has a perfect job, doing a cycle until the field or event in database have been found.
After restart the server in the EM console, the instance's state is running but when i open the trace i can see that the flow is stooped just in the timer event. Timer event only shows "Has been introduced in the activity instance".
Can anyone tell me what's going on?
Thanks

Hi friends
I have a flow where there are three elements:
The first one is a service task that looks for an event in a database using a database adapter
The second is a gateway, if the event was found, the flow continues otherwise the flow goes to a timer event
Timer event waits for 10 minutes and, after that, returns to the first element (the service task).
The flow has a perfect job, doing a cycle until the field or event in database have been found.
After restart the server in the EM console, the instance's state is running but when i open the trace i can see that the flow is stooped just in the timer event. Timer event only shows "Has been introduced in the activity instance".
Can anyone tell me what's going on?
Thanks

ODI Agent and Virtual Servers (VMWare)

Hi
We are planning on moving to virtual servers (VMware product) in the near future.
Has anyone had experience running ODI agent on a virtualised server. I can't envisage any problems, but Oracle do not specificallly support running on VM Ware (as they have their own VM product!!).
Just wondering if theres anyone out there who has already tried this?
Thanks for looking

I agree, seen ODI and agents running on VMWare without any issues on many occasions.
Cheers
John
http://john-goodwin.blogspot.com/

Crypto provider priority reset after restart

We changed the crypto provider priority as mentioned in:
http://help.sap.com/saphelp_nw04/helpdata/en/cd/9dd23e6b2c3d67e10000000a114084/frameset.htm
detail we lowered the iaik provider.
But after restarting the server the settings were reset to default. Is there a way to make the changes permanent ?

Holger the link you provided shows only the way to change the status at startup of some services. It does not show how to change the order in which the providers are loaded.
Sorry I can't be more specific about the SAP server, however if you look at the generic JCE pages on Sun's website they tell you following:
You should have somewhere on your path:
app/user/machine a file name java.security..
In that file you have entries like:
List of providers and their preference orders (see above):
security.provider.1=sun.security.provider.Sun
The number in security.provider.# will determine the order of preference in which the providers are loaded and possibly scanned.
If you want to force a specific provider's implementation of a security protocol you might just have to code for that by requesting it.
exemple Cipher.getInstance(protocol, provider)...
or Cipher.getInstance(protocol, "providername")...

Restart Orchestrator server service failed with error 1053

Hi,
I'm using Orchestrator 6.0. I always get an error 1053 after restart Orchestrator server service.
And no matter how many times I restart my OS, the Orchestrator server service cannot be started any longer.
Does anyone can help on this?
By the way, if I installed a vCenter server 6.0 and Orchestrator 6.0 on a same machine, Orchestrator would always get this error. But if I installed them on different machines, Orchestrator server service can running well sometimes. Is there any limitation when install vCenter server 6.0 and Orchestrator 6.0?
Thanks in advance.
Vicky

Is the orchestrator configurator service running? If so, log in to https://<orchestratorserver>:8283 and take a look on the configuration. If not, take a look to the logs of the vRO service and if you like, post em here.

Nodemanager does not restart managed server after Linux OS reboot

Running Linux 2.6.18, Sun JDK 1.6.0_14, and WebLogic 10.3, we have a correctly functioning nodemanager watching a single managed server. If I kill -9 the managed server, the nodemanager fires up a new one immediately. If, however, we reboot the box, the nodemanager will start cleanly and will not start the managed server. It appears to believe the node should remain down and reports its status as UNKNOWN.
I've seen where this is a known problem on Windows boxes, easily gotten around by supplying the -Xrs parameter to the startup parms for the managed server. (Section 5 of the general nodemanager config doc.) I don't see, however, where there's an equally clean solution for Linux.
Things I've tried:
+ When I set the server to DEBUG, it shows zero sign of receiving a shutdown signal. It's dumping loads of cluster messages, etc, into the log and then suddenly the log just ends so it's dying via kill -9. If the nodemanager is still running at that time, it might try to restart the managed server and log it somewhere as permanently failed.
+ The nodemanager only logs to INFO level, and logs no evidence of deciding to leave the node down. (DEBUG is an invalid LogLevel, so that's all I've got.)
+ A restart signal sent from our AdminServer (on another Linux box) successfully starts the managed node through the nodemanager. Nothing unusual occurs or is logged.
Things I'm curious about:
+ Is there some way to see in what state the nodemanager believes the managed server to be?
+ Is there some value in some doc somewhere that might say the server should not be restarted?
+ Is there not a log of NodeManager client actions? I don't see anything in domain.log or AdminServer.log except when the NM is down.
Thanks,
Kevin
ListenPort=5556
ListenBacklog=50
SecureListener=true
AuthenticationEnabled=true
NativeVersionEnabled=false
CrashRecoveryEnabled=true
JavaHome=/appl/java/jre
StartScriptEnabled=false
StopScriptEnabled=false
StartScriptName=startWebLogic.sh
StopScriptName=
LogFile=/appl/bea/wlserver_10.3/common/nodemanager/logs/nodemanager.log
LogLevel=INFO
LogLimit=0
LogCount=1

can you set NativeVersionEnabled to true. We have faced this in windows which was fixed by changing this property. Some notes from that issue:
Faced this interesting issue in Windows 2008 environment. Managed Servers were started by node manager and it was expected that on a system restart after a crash, the node manager will restore the state of the managed servers to the state it was before the crash. Node Manger was configured to run as a windows service. Hence it started after the server restart. But the individual managed servers were not getting started. Interestingly, for the managed servers started by the node manager there were no <Managed_Server_Name>.lck file in the <Server>/data/NodeManger folder.
To fix this always set the following properties in the nodemanager.properties on the node maager home directory.
CrashRecoveryEnabled=true /* This by default is set to false. This needs to be turned for auto restart after crash to work */
NativeVersionEnabled=true /* This is by default set to true and it should be set as such. If you turn this off on platforms for which weblogic provide native JNI libraries ( e.g. as in Windows 2008) then this wont create the .lck file and hence node manager wont restart the managed server after the crash.
Note: As per official documentation .lck files are required for weblogic node managers to do auto restart after system crash
From Official documentation:
After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.
If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
*/

Mac Mini Server VPN requires restart of service after each reboot

Mac mini Server (Late 2012)
OS X 10.8.4
After a reboot, when viewing in Server.app, VPN service is turned on, however no connections can be made until the service is turned off then back on again.
VPN service log entry shows "Listening for connections..." but doesn't allow incoming VPN calls until the service is restarted.
Anyone else having similar issues or have suggested solutions?
Thanks much!
Jim

Try this
https://discussions.apple.com/message/22564125#22564125

ODI Agent after Restarting/Rebooting Server

Similar Messages

Maybe you are looking for