Hi,
I'd looked at the download section and also with google - but I'm not able to find ODBC drivers for Windows for download anyware ... Can somebody please gie me an URL for?
Thanks
Andre
Hi,
I'd looked at the download section and also with google - but I'm not able to find ODBC drivers for Windows for download anyware ... Can somebody please gie me an URL for?
Thanks
Andre
Hallo,
currently I make an SAP system copy with the following components.
The source system (windows2003):
- SAP instance DEC
- MaxDB Version 7.8.02.23
- MaxDB Studio 7.9.08.00
- The logfile are in the D: drive
The installed target system (windows 2008):
- SAP instance NEW
- MaxDB version 7.8.02.23
- MaxDB Studio 7.9.08.12
- The installation is in the P: drive
The approach is the following:
Action in DEC:
1) DB backup via MaxDB Studio >> backup-file org_dec
Action in NEW:
2) Start with MaxDB Studio 7.9.08.12
3) Initialize the DB
4) Change the db data files from - d:\ ...... to p:\
5) Delete the log file
6) Start the recovery
......but ..the DB disconnect and the recovery stoppt! The error message is: Volume D:\sapdb\DEC\mirrsaplog\M_DISKL001 cannot be created.
The problem is, I can't create a new D: drive in the target system NEW. How is the solution for this problem?
Regards,
Richard
Hi guys,
This is my first question in here, so excuse me if i seem to be in outside of usual formats
Okay, my scenario is this::
I have to call the function UPD_DBCON_ENTRY_SDB from a VBA applcation to update the passwords of CONTROL user of a MAXDB database in R3 connection data (DB11 transaction). The passwords are already changed from DB level. The R3 connection data needs to be updated accordingly with the new passwords. I wrote a piece of code calling the said entry and everything went fine when tested on a kernel release 720 system.
But when i tried testing on another system (i wouldt have gone for a second testing unless by the presure from my peers above ), which is on kernel release 701, it doesnt work. A little troubleshooting showed me that this function module is not Remote-Enabled, but is a Normal Function.
Now what i would like to know is that how do i get the change history for this module, so that i can say that my VBA application will work on a particular version since it has got a remote enabled UPD_DBCON_ENTRY_SDB module.
And thanks in advance for all the help.
Regards,
Lalu George
Hello,
I have a windows system, in the step 11 of 38 the installation is stopped. In the logs show this error,
ERROR 2010-07-28 12:06:27.951
The dbmcli call for action DB_CREATE failed. SOLUTION: Check the logfile XCMDOUT.LOG.
ERROR 2010-07-28 12:06:27.952
The dbmcli call for action DB_CREATE failed. SOLUTION: Check the logfile XCMDOUT.LOG.
ERROR 2010-07-28 12:06:27.952
FCO-00011 The step sdb_create_db_instance with step key |NW_Workplace|ind|ind|ind|ind|0|0|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|ind|3|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0|sdb_create_db_instance was executed with status ERROR .
In the logfile show XCMDOUT.LOG.
> Subprocess starts at 20100728120627
Execute Command : C:\sapdb\programs\pgm\dbmcli.exe -n VBARAHONA inst_enum
Execute Session Command : exit
> Subprocess stops at 20100728120627
OK
7.8.01.14 C:\sapdb\VIC\db
Regards
Hi,
I have installed SAP Netweaver developer Studio 6.40 which installed MAXDB database also. Due to some reason I had to unistall the trial version of Developer studio, in this process developer studio got unistalled but not MAXDB.
*----
I use Add/Remove programs and uninstall MaxDB. I get the messages like this.....
Start uninstallation now (y/n) : Y (resoponse)
then message displays
found instance of J2E, cannot remove package..first remove all instances...
*----
I have stopped all the services, even then Iam getting such error message. How do I uninstall?
Help needed.
-Suresh
Hello,
i tried to migrate an existing Hibernate Application from PostgreSQL to MaxDB.
The first problem, i already solved, was that Hibernates default SAPDBDialect doesn't supports identity columns.
After searching a while, i found the following solution to provide MaxDBs serial support with hibernate: https://hibernate.atlassian.net/browse/HHH-7324
Now the schema update runs successfully and all tables were created, but when i try to persist the first entity, the following error occurs:
2013-09-02 09:42:35,040 WARN [Thread-3] org.hibernate.engine.jdbc.spi.SqlExceptionHelper: SQL Error: 0, SQLState: null
2013-09-02 09:42:35,040 ERROR [Thread-3] org.hibernate.engine.jdbc.spi.SqlExceptionHelper: An SQLException was provoked by the following failure: java.lang.UnsupportedOperationException: Method prepareStatement() is not yet implemented.
2013-09-02 09:42:35,050 ERROR [Thread-3] seetec.logistic.modules.server.hibernate.HibernateEntityManager: Exception in HibernateEntityManagerImpl.save!
org.hibernate.exception.GenericJDBCException: An SQLException was provoked by the following failure: java.lang.UnsupportedOperationException: Method prepareStatement() is not yet implemented.
at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:54)
at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:125)
at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:110)
at org.hibernate.engine.jdbc.internal.proxy.ConnectionProxyHandler.continueInvocation(ConnectionProxyHandler.java:146)
at org.hibernate.engine.jdbc.internal.proxy.AbstractProxyHandler.invoke(AbstractProxyHandler.java:81)
at $Proxy26.prepareStatement(Unknown Source)
at org.hibernate.engine.jdbc.internal.StatementPreparerImpl$2.doPrepare(StatementPreparerImpl.java:105)
at org.hibernate.engine.jdbc.internal.StatementPreparerImpl$StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:166)
at org.hibernate.engine.jdbc.internal.StatementPreparerImpl.prepareStatement(StatementPreparerImpl.java:103)
at org.hibernate.id.insert.AbstractSelectingDelegate.performInsert(AbstractSelectingDelegate.java:55)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2768)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:3279)
at org.hibernate.action.internal.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:81)
at org.hibernate.engine.spi.ActionQueue.execute(ActionQueue.java:362)
at org.hibernate.engine.spi.ActionQueue.addResolvedEntityInsertAction(ActionQueue.java:203)
at org.hibernate.engine.spi.ActionQueue.addInsertAction(ActionQueue.java:183)
at org.hibernate.engine.spi.ActionQueue.addAction(ActionQueue.java:167)
at org.hibernate.event.internal.AbstractSaveEventListener.addInsertAction(AbstractSaveEventListener.java:320)
at org.hibernate.event.internal.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:287)
at org.hibernate.event.internal.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:193)
at org.hibernate.event.internal.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:126)
at org.hibernate.event.internal.DefaultPersistEventListener.entityIsTransient(DefaultPersistEventListener.java:208)
at org.hibernate.event.internal.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:151)
at org.hibernate.event.internal.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:78)
at org.hibernate.internal.SessionImpl.firePersist(SessionImpl.java:844)
at org.hibernate.internal.SessionImpl.persist(SessionImpl.java:819)
at org.hibernate.internal.SessionImpl.persist(SessionImpl.java:823)
...
Caused by: java.sql.SQLException: An SQLException was provoked by the following failure: java.lang.UnsupportedOperationException: Method prepareStatement() is not yet implemented.
at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:106)
at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:65)
at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:62)
at com.mchange.v2.c3p0.impl.NewPooledConnection.handleThrowable(NewPooledConnection.java:369)
at com.mchange.v2.c3p0.impl.NewProxyConnection.prepareStatement(NewProxyConnection.java:416)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.hibernate.engine.jdbc.internal.proxy.ConnectionProxyHandler.continueInvocation(ConnectionProxyHandler.java:138)
... 29 more
Caused by: java.lang.UnsupportedOperationException: Method prepareStatement() is not yet implemented.
at com.sap.dbtech.jdbc.ConnectionSapDB.prepareStatement(ConnectionSapDB.java:1499)
at com.sap.dbtech.jdbc.trace.Connection.prepareStatement(Connection.java:262)
at com.mchange.v2.c3p0.impl.NewProxyConnection.prepareStatement(NewProxyConnection.java:399)
... 34 more
I'm using Hibernate 4.1.5 SP1 with MaxDB 7.7.06 and it seems that the class "ConnectionSapDB" in the MaxDB JDBC-Dirver doesn't implement the method prepareStatement( sql, autoGeneratedKeys );
Manually inserting records with sql and a normal PreparedStatement works and the id is also generated automatically.
Has someone an idea how to solve this problem?
Thank you.
Hi Gurus,
One of our development systems was recently upgraded to EHP5. We had also completed the upgrade using one sandbox system which is a copy of DEV system.
After the systems were upgraded to EHP5, we are finding that the Program RFCEXEC vanishing from EXE directory. And Because of this, XI connectivity fails. Is this due to the EHP5 upgrade? Please help me in this.
Thanks
Ranga
Hi All ,
I am trying to install SAP trial version . While installation of MAXDB serve , I am getting an error " Some database application might still be running"
I dont have any other database installed on my system .
Kindly reply what can be the possible reason for this .
Thanks n Regards
Manik L Dhakate
Hi all,
I have installed liveCache on MaxDB.
During SNP planning I'v reciving dump - /sapapo/stockanc does not exist.
I'm checking through LC10 - command db_execute select * from /sapapo/stockanc
And it returns that there is no such table.
Do not know what to do. I'm thinking to create this table manually. But do not know what is the tabke structure...
Can anyone hint this?
May I know steps and coding to access ODBC datasource from ABAP?
Hello experts,
We are doing our SCM upgrade from 4.1 to 7.0 with migration. We have completed with the upgrade but before doing the LC upgrade we need to upload the data to the LC using the /SAPAPO/OM_LC_UPGRADE_70, while doing this it gives an error for connectivity to the LC. From DB59, i checked the connection test fails for "Native SQL" (LCA) step.
+1. Connect. test with "dbmcli db_state" Successful+ +2. Connect. test with command mode "dbmrfc db_state" Successful+ +3. Connect. test with session mode "dbmrfc db_state" Successful+ +4. Connect. test with "native SQL" ( LCA ) No connection+ +SQL Code:+ +Error creating a secondary database connection+ +Set up of a secondary connection to the database system failed. It is possible that the data required for setting up the con+ +SQL code:+ +For detailed information, see the developer trace for work process: 4+
From the workprocess we get the below error
B Loading DB library '/usr/sap/EAD/DVEBMGS59/exe/dbsdbslib.o' ... M *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/EAD/DVEBMGS59/exe/dbsdbslib.o") FAILED "#0509-130 Symbol resolution failed for /usr/sap/EAD/DVEBMGS59/exe/dbsdbslib.o because: #0509-136 Symbol getData__Q2_6SQLDBC10SQLDBC_LOBFPvPLLT3T1T3T2b (number 197) is not exported from ## dependen" (errno=8,Exec format error) [dlux.c 445] M {root-id=4D87070E166501B0E1008002A7E41451}_{conn-id=00000000000000000000000000000000}_0 B *** ERROR => Couldn't load library '/usr/sap/EAD/DVEBMGS59/exe/dbsdbslib.o' [dbcon.c 5263] B {root-id=4D87070E166501B0E1008002A7E41451}_{conn-id=00000000000000000000000000000000}_0 B ***LOG BYG=> could not load library for database connection LCA [dbds 886]
We have upgrade the sap kernel and also the above said dbsl library, and it exists in the exe directory, But still nothing seems to work...
Can someone give any ideas ??
Thx
Ananth
Hi Guys,
MaxDB provides the possibility to logically unite several database objects (e.g. Tables, Views, Indexes, ...) in so called "Schemas".
However, I couldn't find any documentation about how to connect to a certain schema via JDBC. How should the JDBC URL look like? Assuming I have this kind of URL jdbc:sapdb://localhost:7200/MAXDB. Is there a way to connect to the schema "DEMO"?
Thanks for the help.
Cheers,
Gerardo
Hi All,
when I'm trying to start liveCache I'm getting an error: "Cannot open SQL connection to liveCache LCA".
Operational state is online.
Kernel - 7.7.07
Next steps are successful:
"LC10 -> liveCache monitoring -> Tools -> dbmcli ::
a) sql_execute select * from users"
From Alert monitor I see an error: "Instance ONLINE, but no SQL access possible". If i try connection test, thenI see:
"
1. Connect. test with "dbmcli db_state" Successful
2. Connect. test with command mode "dbmrfc db_state" Successful
3. Connect. test with session mode "dbmrfc db_state" Successful
4. Connect. test with "native SQL" ( LCA ) No connection
SQL Code: 4025
For detailed information, see the developer trace for work process: 2
"
How to see this developer trace I do not know...
Hi,
Is there any table through which we can find whether the live cache is acitve or inactive.
Thanks,
Siva.
Hi,
After an upgrade from SCM5.0 to SCM 7.0 EHP2 SPS6, I am trying to upload the master data to livecache (/SAPAPO/OM_LC_UPGRADE_70, section C, 3). Job RESOURCE_LC_CLIENT_020 ends in error. The spool displays the following:
17.133 Single resources can only have available capacity of 0 or 1
17.133 Single resources can only have available capacity of 0 or 1
17.133 Single resources can only have available capacity of 0 or 1
17.133 Single resources can only have available capacity of 0 or 1
17.133 Single resources can only have available capacity of 0 or 1
17.133 Single resources can only have available capacity of 0 or 1
The database logging /sapdb/SLQ/data/wrk/SLQ/lcapo_com_trace_01.txt shows this message:
0x62c330 00000006 APS_PLAN_VERSION_CHANGE DDIC 20130730-222049 Signature: 1f820181
0x1f820181 20130730-222049 [PLV] incident id: HBnT0G00000400000JWAS0
0x1f820181 20130730-222049 [PLV] PlanVersion::create: duplicate planversion 020, NULL_GUID user DDIC Corre@
0x1f820181 sponding schema also exists. PlanVersion cannot be created
The livecache version is 7.9.08.07, also for the client.
I tried to reinitialize the livecache and import again, but it did not help.
I tried with another user, but it did not help.
In the development system, I did not get this issue.
I am looking forward to your reply.
Kind regards,
Marc
Hi,
I'd looked at the download section and also with google - but I'm not able to find ODBC drivers for Windows for download anyware ... Can somebody please gie me an URL for?
Thanks
Andre
Hello,
i am trying to install php-5.4.13 with MaxDB ext.
configuring with the Option: --with-maxdb=/opt/sdb/programs/
It can be configured but then i get a lot of Errors,
thanks alot for you help
[root@sh php-5.4.13]# make
Makefile:783: warning: overriding commands for target `ext/maxdb/php_maxdb.lo'
Makefile:781: warning: ignoring old commands for target `ext/maxdb/php_maxdb.lo'
/bin/sh /usr/src/php-5.4.13/libtool --silent --preserve-dup-deps --mode=compile cc -Iext/maxdb/ -I/usr/src/php-5.4.13/ext/maxdb/ -DPHP_ATOM_INC -I/usr/src/php-5.4.13/include -I/usr/src/php-5.4.13/main -I/usr/src/php-5.4.13 -I/usr/src/php-5.4.13/ext/date/lib -I/usr/src/php-5.4.13/ext/ereg/regex -I/usr/include/libxml2 -I/usr/include/freetype2 -I/opt/sdb/programs//sdk/sqldbc/incl -I/usr/src/php-5.4.13/ext/sqlite3/libsqlite -I/usr/src/php-5.4.13/TSRM -I/usr/src/php-5.4.13/Zend -I/usr/include -g -O2 -fvisibility=hidden -c /usr/src/php-5.4.13/ext/maxdb/php_maxdb.c -o ext/maxdb/php_maxdb.lo
In file included from /usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:100:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.h:203: error: duplicate âstaticâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.h:208: error: duplicate âstaticâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.h:215: error: duplicate âstaticâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_link_affected_rows_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:257: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_link_client_version_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:259: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_link_connect_errno_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:260: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_link_errno_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:262: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_link_field_count_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:264: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_link_insert_id_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:267: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_link_protocol_version_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:268: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_link_server_version_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:270: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_link_thread_id_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:272: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_link_warning_count_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:273: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_result_type_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:275: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_result_current_field_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:276: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_result_num_rows_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:277: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_stmt_affected_rows_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:280: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_stmt_insert_id_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:281: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_stmt_num_rows_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:282: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_stmt_param_count_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:283: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_stmt_field_count_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:284: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_stmt_errno_readâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:285: warning: comparison is always true due to limited range of data type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: At top level:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:335: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âmaxdb_link_methodsâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:386: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âmaxdb_result_methodsâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:408: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âmaxdb_stmt_methodsâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:484: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âmaxdb_functionsâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:600: error: âmaxdb_functionsâ undeclared here (not in a function)
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âphp_maxdb_fetch_hashâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:1714: error: âzend_fcall_infoâ has no member named âobject_ppâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:1751: error: âzend_fcall_info_cacheâ has no member named âobject_ppâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_read_propertyâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:1929: error: âzvalâ has no member named ârefcountâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:1935: error: too few arguments to function âstd_hnd->read_propertyâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_write_propertyâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:1969: error: âzvalâ has no member named ârefcountâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:1970: error: âzvalâ has no member named ârefcountâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:1975: error: too few arguments to function âstd_hnd->write_propertyâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âmaxdb_objects_newâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:2088: error: âzend_class_entryâ has no member named âdefault_propertiesâ
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âzm_startup_maxdbâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:2129: warning: assignment from incompatible pointer type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:2130: warning: assignment from incompatible pointer type
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:2135: error: âmaxdb_link_methodsâ undeclared (first use in this function)
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:2135: error: (Each undeclared identifier is reported only once
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:2135: error: for each function it appears in.)
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:2142: error: âmaxdb_result_methodsâ undeclared (first use in this function)
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:2148: error: âmaxdb_stmt_methodsâ undeclared (first use in this function)
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c: In function âzif_maxdb_stmt_bind_paramâ:
/usr/src/php-5.4.13/ext/maxdb/php_maxdb.c:5483: warning: âzend_get_parameters_exâ is deprecated (declared at /usr/src/php-5.4.13/Zend/zend_API.h:238)
make: *** [ext/maxdb/php_maxdb.lo] Error 1
hi,
/SAPAPO/OM_DELETE_OLD_SIMSESS - periodic job fails says as below log. I could not find OSS note in my search.
Looks to me, the lock corresponds to a simulation version is missing. Job tries to delete simulation version/ lock together.. however it fails.
If this is the case, how to clear old SIMM versions?
Job Log:
07/21/2011 08:31:13 JYKhRvRmN6dX0000f6VRCW lock does not exist
07/21/2011 08:31:14 Cannot delete simulation version
07/21/2011 08:31:14 Job cancelled after system exception ERROR_MESSAGE
Thanks,
RajS
Hi we are frequently getting this error Live cache lock handler not available and this causes our process chains to fail.
Can anyone please explain in details what this error refers to and direct to any good links for error resolution.