I am using liferay 6.1 and while configuring the database to mysql database in console it is giving error as innoDB is having row level logging enabled so unable to execute the query...etc..
But surprisingly I am not able to see these logs in any of the files.
I have checked {TOMCAT_HOME}/logs directory and {LIFERAY_HOME}/logs directory. But none of the files are containing the error logs.
If anybody can assist me on is there any other place to look for the logs, that will be really helpful.
Shruti
The blank database you have created might not have enough permission, you would need to give full permission i.e. to allow write / execute.
So that while you configure Liferay to point this blank database it will create table which requires write permission.
The issue is resolved now.
In mysql db the setting for binlog_format is "STATEMENT'
I changed it to ROW and it started running.
The syntax:
SET GLOBAL binlog_format = 'ROW';
Thanks ..
Related
Liferay 6.1.1 CE GA2 works works fine-and-dandy on my local machine and my coworkers as well. When we deploy it to our main dev server, we find that we can't save any changes (i.e., create web content, change theme/schemes, etc).
Any idea why this is happening?
Cheers!
check the log output, this might give you hints on what's going wrong
If you get UI errors, this might help as well
check what database you're connecting with, make sure that the user account you use has write access to the database
In case you use hsql (don't do this unless on an unimportant demo server) make sure that the user your appserver runs as is able to write to the data directory and persist the database
If you're running on a cluster and the second machine doesn't pick up changes made through the first machine, you need to configure clustering properly. The Userguide at https://www.liferay.com/documentation/ has a chapter on this.
If nothing of this helps, please give more information
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've created a portal-ext.properties and added:
jdbc.default.driverClassName=oracle.jdbc.driver.OracleDriver
jdbc.default.url=x
jdbc.default.username=y
jdbc.default.password=z
schema.run.enabled=true
schema.run.minimal=true
And I've added my ojdbc5.jar to lib/ext.
However when I run my startup.bat the database isn't being generated?
Does anyone know why this is occuring?
Check to make sure that the database is up and running. Can you log into Oracle using SQL*Plus or some other client using the credentials you've provided? If you can't, Liferay won't be able to either.
Can you try using lifery's Data Migration feature? You can start your server with default HSQL script and then try to migrate (which can automatically create tables as well).
Go to Control Panel->Server Administration.
- Enter the values in section Migrate from One DB to another and click execute.