For eval purpose; I installed Cognos 8.4.1 on Ubuntu 10.04.
The DB for the content store is Oracle 11g with AL32 UTF8 character set.
Crypto keys are stored locally. Env is set as recommended.
When trying to start the service, even before creating the content store, I get this message :
CM-CFG-5076 A Content Manager configuration error occurred during the initialization of Cognos Access Manager. CAM-AAA-0071 An internal error occurred. St9bad_alloc
Any idea of the cause ?
Thanks,
Fred
Using a supported distribution would definitely be a good idea. That said, if you stop cognos, rename the cogserver.log file (by default this is in /logs under your installation directory), start cognos up again and post the generated log file we might get more detail about what's stopping it.
Related
I am facing below issue while connecting to DB server(Suse linux machine B) from app Server (Suse linux machine A) which is contains WEbSphere Application Server, configured with DB2. please find below details.
ASX7015E: Exception running command: "AdminControl.testConnection('DB_NAME(cells/cell_name/nodes/node_name/servers/server1|resources.xml#dataSource_ID)')"; exception information:
com.ibm.websphere.management.exception.AdminException
javax.management.MBeanException
java.sql.SQLNonTransientException: java.sql.SQLNonTransientException: null DSRA0010E: SQL State = 08001, Error Code = -1,639.
not able to find root-cause of this error
not able to find, from which server this error came.
Note : This issue came after doing some path update on production issues. WebSphere version is 9.0, using websphere internal java and openJPA 2.0 and DB2 version is 11.1.0.0.
The sqlode -1639 is caused by incorrect permissions on files on the Db2-server.
See this technote
The advice given there, in case of broken links, is:
Cause
This is caused by incorrect permissions and ownership of the following security files in ~/sqllib/security directory
db2chpw
db2ckpw
These files should have root as owner and must have permission -r-s--x--x
Resolving The Problem
Change the owner of the files to root
Change the permission of the files to -r-s--x--x
Update the instance using db2iupdt
Apart from the above, it is always unwise to use any "fixpack 0" of any Db2 product to production environments on linux/unix/windows. There are always too many silly bugs that have long since been fixed by subseqent cumulative fixpacks. Your question mentions v11.1.0.0 (this is fixpack 0 of Version 11.1 ). Best advice is to deploy the current most recent fixpack to the Db2-server, so get your DBA to do this first on your development/test environments before deploying to production.
Additionally consider ensuring to maintain the Db2 jdbc driver version on your WAS server, instead of continuing to use the (usually old version) that comes with WAS. Best practice is to keep the version of the jdbc driver the same between the WAS and the Db2-server, so keep those versions maintained.
Just started to use LogParser. Already existing system is using log parser to read the IIS file and update the db to calculate hits, etc..
I am trying to understand the flow and need to extract two more new fields from IIS log and update the db.
In my local desktop i do have sample log file and log parser. And i tried this query LogParser.exe “Select top 10 * from c:\LogParser*.log” in Log parser and got Error: detected extra argument "top" after query. Why i couldnt read the log file which is existing in my local?
And also i got batch file which is in the production. i changed the path to access my desktop files and scheduled the windows task. It is also not working. The code as,
logparser file:Extract.sql?inputfile=c:\LogParser*.log -o:SQL -database:dbname server:test1 -username:username -password:password -createtable:OFF -maxStrFieldLen:2048 -clearTable:OFF
I just need to simulate the existing system to update the database and need to add more fields.
Please help me to go further. i really got stuck.
I am not sure, if this would solve your problem, you can try your hands at LogParser Studio - that gives an IDE to the traditional Log Parser.
Definitely easier to rectify your common mistakes, and get help/documentation at your disposal. You can get more info and download it from here.
Hope it helps!
I am trying to create an instance using the Configuration Manager of WCS 7. I am working on a Win 7 x64 machine with DB2 9.5 64 bit version.
I am struck with this Massloading error when the instance creation happens :
In createInstanceANT.log file :
[Massload] Massloading
C:\IBM\WebSphere\CommerceServer\schema\xml\wcs.keys.xml Error in
MassLoading, please check logs for details.
The error log shows the following error :
[jcc][10165][10044][4.3.111] Invalid database URL syntax:
jdbc:db2://:0/WCSDEMO. ERRORCODE=-4461, SQLSTATE=42815
C:\IBM\WEBSPH~1\COMMER~2\config\DEPLOY~1\xml\createBaseSchema.xml:185:
Error in massloading
WCSDEMO is the database name. The Massloader is not able to get the URL and port to connect. It is supposedly getting them from createInstance.properties file but it is not working. The createInstance.properties file has all the details of the DB to connect.
What could be the reason for this error and how to resolve it ? Is there any configuration change that I am missing ?
Can you provide some more details.
look inside the messages.txt file located in WC_install_dir/instances/instance_name/logs
and confirm what the exact issue is. If it is related to jdbc driver being wrong I may be able to help you.
I've been running into massloading problems with external systems. Eg. databases not on the same machine as the WAS installation.
In these cases I look for the
As you can see setting the loaderDBName to just the name of the database would look on the local machine. But by changing this statement so you load with the syntax
loaderDBName=[DATABASE_SERVER_NAME]:[PORT]/[DATABASE_NAME]
You'll be able to massload using the commerce standard scripts. These changes needs to be done in many scripts. Both for updating fixpacks and enabling features. If you run database updates without the changes it will crash at first and have done all the schema changes to the database that you then need to comment out before trying again.
IBM Software Support is your friend. They'll help you fix it.
I am facing a problem while starting the websphere message engine for one of the application deployed on websphere. This application is getting deployed automatically as a part of the installation of Websphere Lombardi 7.2 express edition. It's using websphere 7 internally to deploy it. When I try to start the message engine from the administrative console of websphere I am getting following error:
The messaging engine ProcessCenter01.twperfsvr-twperfsvr_bus cannot be started as there is no runtime initialized for it yet, retry the operation once it has initialized. For the runtime to successfully initialize the hosting server must be started, have its 'SIB service' already enabled, and dynamic configuration reload enabled. If this is a newly configured messaging engine and it is the first messaging engine to be hosted on this server, then it is most likely the 'SIB service' was not previously enabled and thus the server will need to be restarted. The messaging engine runtime might not be initializing because of an error while trying to start, examine the SystemOut.log of the hosting server to check for error messages indicating the problem.
After restarting the server, the same error shows. Can anyone help me to to find what gets loaded as a part of "initialization of runtime"? Are there any config files etc. that I need to check to solve this issue? I am suspecting some missing configuration causing error to load the runtime for this particular application.
I too faced this issue today had to delete all the files under the message store
check the directory-file path mentioned in
Application servers > server1 > Messaging engines > XXX.server1-primaryBus > File store
Just Enable the SIB Services For the particular Server.
Example:Server-->Application Server-->click on Server Name-->right hand side we can see SIB services-->Check box the Enable services.
This will solve your problem
Recently I have faced the same issue when I rebuilt the jvms in UAT envt. After searching on web I found that because of the old messages saved in the message store(flat files in my envt) the messaging engines was not getting initiated. After deleting the old messaging store and restarting the servers it got initialized.
I have struggled with this problem too.
In our situation the problem was that the file message store location was used that was already created for a different (or old) message-engine.
If you add a busmember to the service-bus and use a file store implementation, then you need to supply the path for the store and log folder. Make sure these locations don't exist yet, other wise you will run in the problem above. The message-engine for this member will use these folders.
If you have a script for creating the message-bus infrastructure, make sure that when you delete the bus or remove message-engines, that you remove the file store/log folders for these, before you re-run your script.
Another possibility is that you are using a external database as a data store, and the user that is used for the connection is not allowed to create a database. You might find a ffdc entry like this:
DB2 SQL Error: SQLCODE=-552, SQLSTATE=42502, SQLERRMC=DB2ADMIN;CREATE
SCHEMA, DRIVER=3.61.65
Then you have to go to your database administration tool and give DB2ADMIN the proper privileges. Then restart the server or cluster.
Finally this issue is been resolved. I did not create the schema in SQL Server with same name as that of the username I gave to connect SQL Server during the installation of WLE 7.2
Please find details about this at below link:
http://www.ibm.com/developerworks/forums/message.jspa?messageID=14795282
I have recently been receiving the following error whenever I am asked to supply the host username and password in Oracle DataGuard's Enterprise Manager (EM) tool: RemoteOperationException: Error reading error from command. Any configuration or management that needs to be performed and requires the host credentials is throwing this error. This is one of the most unhelpful errors I have seen in a long time. I have checked all of the log files I can think of and I can't find any error logs or indications to the problem. I verified that I can log into the servers with the credentials that I was trying in EM, I verified the connection configuration through EM using the built in test tools, and I verified that all of the saved passwords in EM were correct. This was working on the initial installation. Sometime over the last couple of weeks it stopped working and I'm not sure why. The hosts are running Linux Red Hat 4 Enterprise and Oracle 10g.
Reinstalling the OEM agents fixed this issue. Somehow, all of the agents seemed to be corrupt.