TimesTen restore/re-attach

Hi,
I'm new in TimesTen and have a problem.
We lost sys.odbc.ini file and server DSN to TimesTen database.
After sys.odbc.ini restore I tried to add new DSN record which should be (similar) same as loosed one. After that use ttIsql to connect to new DSN, but there is error:"836: Cannot create data store shared-memory segment, error 22". After that tried to connect to some examle database, but get same error.
After server (mashine) restart error still exist for all databases.
Do you know someone what should be done for database restore/re-attach ?
Thanks in advance:
Krastio Kostov

In your original post you said that some of the other example datastores were also exhibiting this problem. Is that still the case after shmmax was increased?
Error 22 is EINVAL and shmget() only returns this if the size of segment we are requesting is invalid based on SHMMIN and SHMMAX. This would mean that the values in the datastore that determine the size of the segment required (PermSize, TempSize, LogBuffSize) exceed SHMMAX when added together. Are you still getting the original error or do you now get a different error after you increased shmmax? Perhaps you could post your ODBC.INI settings for the datastore in question plus the output of the ttVersion command and the current setting that you have for shmmax.
Thanks, Chris

Similar Messages

Hi ! Backup, Restore and attach database!

Hi all !
I'm stuyding SAP Business One for a month.
In SAP, i don't know, how do i backup, restore, attach database?
Please tell me !
Thanks and Rgds !

Hi,
Ignore this error.
Just use DBUA from 10.2.0.5 directly after error (ORA-39700) be raised by RMAN, DBUA will perform all tasks required and will perform the upgrade of the database..
I've done this many times
Regards,
Levi Pereira
Edited by: Levi Pereira on Jul 30, 2011 10:25 AM

How to restore or attach database

Hi all,
I had installed oracle 9.i on PC01 computer, then I created database is KT01 at C:\oracle\oracledata\KT01 path.
Unfortunately, PC01 has died, but I didn't backup KT01 database. so I must install oracle 9.i on PC02 computer, and copy KT01 folder that contain data in PC01 to PC02.
- if I create database with the same name and path is C:\oracle\oracledata\KT01 on PC02, and copy KT01 database from PC01 to overwrite on PC02. then mount and start KT01 database, it is ok.
- if I create database with the same name, but difference path (example: D:\oracle\oracledata\KT01) on PC02, and copy KT01 database from PC01 to overwrite on PC02. then mount and start KT01 database. it is not run, how can I sovle this problem
- in case, oracle in PC01 is version 8.x, but oracle version in PC02 is 9.i, How can I do it.
please help me, thanks.
Nguyen

Hi.
If you have all datafile from original database you can simply move all files from pc01 to kt01 in a folder you decide.
Than you have to recreate the controlfiles. You need to change the initialization parameter file so that the controlfile parameter points to the new location. Also when moving the files over you need only the datafiles. Controlfile is recreated aswell as the redolog files when doing a open resetlogs. If you want to change the database name, you substitute the
CREATE CONTROLFILE REUSEwith
CREATE CONTROLFILE SETBelow is an example of recreation of controlfiles using the resetlogs option:
(Substitute the datafile and redo log locations)
# Set #2. RESETLOGS case
# The following commands will create a new control file and use it
# to open the database.
# The contents of online logs will be lost and all backups will
# be invalidated. Use this only if online logs are damaged.
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "DBTEAM" RESETLOGS NOARCHIVELOG
-- SET STANDBY TO MAXIMIZE PERFORMANCE
MAXLOGFILES 5
MAXLOGMEMBERS 5
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 3176
LOGFILE
GROUP 1 (
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_REDO_1A.LOG',
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_REDO_1B.LOG'
) SIZE 10M,
GROUP 2 (
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_REDO_2A.LOG',
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_REDO_2B.LOG'
) SIZE 10M,
GROUP 3 (
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_REDO_3A.LOG',
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_REDO_3B.LOG'
) SIZE 10M
-- STANDBY LOGFILE
DATAFILE
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_SYSTEM_1.DBF',
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_UNDO_1.DBF',
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_TOOLS_1.DBF',
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_DESIGNER_DATA_1.DBF',
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_DESIGNER_INDEX_1.DBF',
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_SYSDOC_DATA_1.DBF',
'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_SYSDOC_INDEX_1.DBF'
CHARACTER SET WE8ISO8859P1
# Recovery is required if any of the datafiles are restored backups,
# or if the last shutdown was not normal or immediate.
RECOVER DATABASE USING BACKUP CONTROLFILE
# Database can now be opened zeroing the online logs.
ALTER DATABASE OPEN RESETLOGS;
# Commands to add tempfiles to temporary tablespaces.
# Online tempfiles have complete space information.
# Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP ADD TEMPFILE 'D:\ORACLE\ORADATA\DBTEAM\DBTEAM_TEMP_1.DBF'
SIZE 52428800 REUSE AUTOEXTEND ON NEXT 10485760 MAXSIZE 1048576000 ;
# End of tempfile additions.
It is not possible to clone a database between versions. If you want to upgrade to 9i, you should probably startup the database on 8i, do an export as system user and import it into a newly created 9i database. Or use the direct upgrade path from metalink.
Good luck
Rgds Kjell

Restoring or attaching the *.mdf file

Hai,
I am trying to attach the *.mdf file then i am getting the error 1813.
The problem occurs when our development database transcation running out of memory disk, then I dettach database and at the time of dettaching database some of users are connected. I kill the session of all users.
After I deleted the log file. Now when i am trying to attach the database then I am getting the error no 1813.
Anybody urgent reply

1) move the existing .MDF file to a new location (to backup)
2) Start SQL Server Enterprise manager, and create a new (dummy) database where the .MDF file is the exact same name and size of your old/existing .MDF. The ldf file can remain at 1mb in size. 3) Stop the SQL Server service and copy only the .MDF to the location of the new/dummy .MDF file. 4) Start SQL Server. At this point, the database should come up as suspect. You will then want to place the database into emergency bypass mode and rebuild the Transaction log. This can be accomplished by performing the following steps: a) Change the database context to Master and allow updates to system tables. Note you will be performing this within Query Anayzler:
Use Master
go
sp_configure 'allow updates',1
reconfigure with override
go
b) Set the database in emergency bypass mode:
Select dbid, name, status from sysdatabases where name = '<database name>'
-- Note the value of status and write it down for future reference
begin tran
update sysdatabases set status = 32768 where name = '<database name>'
commit tran
c) Stop and restart your SQL Server. At this point, the database will come up in emergency mode. At this point, you will be able to browse, but not update any data within the database. d) We will now want to rebuild the log/ldf file. To do this, you will want to run the following: DBCC rebuild_log('<database name>','')
If you do not receive any errors, we will want to reset the status of the database by running the following commmand and restarting SQL Server:
use master
exec sp_dboption 'database name','single user',true
go
begin tran
update sysdatabases set status = 0 where name = '<database name>'
commit tran
e) set database option to not allow updates to the system tables: sp_configure 'allow updates', 0
reconfigure with override
go
f) stop and restart SQL Server
When the server restarts, you will then want to launch Query Analyzer and run the following to validate the database and check the overall integrity: use master
go
sp_dboption '<database name>','Single user',true
You will then want to run the following:
DBCC checkdb('<database name>')

Cannot attach data store shared-memory segment using JDBC (TT0837)

I'm currently evaluating TimesTen during which I've encountered some problems.
All of the sudden my small Java app fails to connect to the TT data source.
Though I can still connect to the data source using ttisql.
Everything worked without problems until I started poking around in the ODBC administrator (Windows 2K).
I wanted to increase permanent data size so I changed some of the parameters.
After that my Java app fails to connect with the following message:
DriverManager.getConnection("jdbc:timesten:direct:dsn=rundata_tt60;OverWrite=0;threadsafe=1;durablecommits=0")
trying driver[className=com.timesten.jdbc.TimesTenDriver,com.timesten.jdbc.TimesTenDriver@addbf1]
SQLException: SQLState(08001) vendor code(837)
java.sql.SQLException: [TimesTen][TimesTen 6.0.4 ODBC Driver][TimesTen]TT0837: Cannot attach data store shared-memory segment, error 8 -- file "db.c", lineno 8846, procedure "sbDbConnect()"
The TT manual hasn't really provided any good explanation what the error code means.
Obviusly I'v already tried restoring the original ODBC parameters without any luck.
Ideas..anyone?
/Peter

Peter,
Not sure if you have resolved this issue or not. In any case, here are some information to look into.
- On Windows 32-bit, the allocation of shared data segment doesn't work the same way like on Unix and Linux. As a result, the maximum TimesTen database size one can allocate is much smaller on the Windows platform than on other platforms.
- Windows error 8 means ERROR_NOT_ENOUGH_MEMORY: not enough storage is available to process this command.
- TimesTen TT0837 says the system was unable to attach a shared memory segment during a data store creation or data store connection operation.
- What was the largest successful perm-size and temp-size you used when allocating the TimesTen database?
* One explanation for why you were able to connect using ttIsql is that it doesn't use much of the DLLs, whereas your Java application typically has a lot more DLLs.
* As a troubleshooting step, you can try reduce your Temp-size to a very small size and just see if you can connect to the data store. Eventually, you may need to reduce your perm-size to get Windows to fit the shared data segment in the process space.
By the way the TimesTen documentation has been modified to document this error as follows:
Unable to attach to a shared memory segment during a data store creation or data store connection operation.
You will receive this error if a process cannot attach to the shared memory segment for the data store.
On UNIX or Linux systems, the shmat call can fail due to one of:
- The application does not have access to the shared memory segment. In this case the system error code is EACCESS.
- The system cannot allocate memory to keep track of the allocation, or there is not enough data space to fit the segment. In this case the system error code is ENOMEM.
- The attach exceeds the system limit on the number of shared memory segments for the process. In this case the system error code is EMFILE.
It is possible that some UNIX or Linux systems will have additional possible causes for the error. The shmat man page lists the possibilities.
On Windows systems, the error could occur because of one of these reasons:
- Access denied
- The system has no handles available.
- The segment cannot be fit into the data section
Hope this helps.
-scheung

Cannot attach PL/SQL shared memory error

Hi everybody,
I got the following error when trying to reconnect the same Java process to a Timesten instance that has been restored after failure:
java.sql.SQLException: [TimesTen][TimesTen 11.2.2.6.0 ODBC Driver][TimesTen]TT8521: Cannot attach PL/SQL shared memory; virtual memory at PLSQL_MEMORY_ADDRESS already in use by TimesTen -- file "db.c", lineno 9924, procedure "sbDbConnect"
at com.timesten.jdbc.JdbcOdbc.createSQLException(JdbcOdbc.java:3238)
at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3387)
at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3352)
at com.timesten.jdbc.JdbcOdbc.SQLDriverConnect(JdbcOdbc.java:801)
at com.timesten.jdbc.JdbcOdbcConnection.connect(JdbcOdbcConnection.java:1866)
As I has understood from the Timesten Error 8521, I have to rollback and close each direct Timesten connection in my app. I implemented the solution, but it didn't help.
My app has tho copies of a database: local and remote, and two connections to these DBs: one is direct and the second is client. The last one is used as backup for the case when the direct connection is broken.
XLA is used for monitoring data changes on the local DB.
The question is: may be these XLA subscriptions prevent the shared memory segments from being released? What should I do to avoid the error 8521 during failback?

Hi everybody,
I got the following error when trying to reconnect the same Java process to a Timesten instance that has been restored after failure:
java.sql.SQLException: [TimesTen][TimesTen 11.2.2.6.0 ODBC Driver][TimesTen]TT8521: Cannot attach PL/SQL shared memory; virtual memory at PLSQL_MEMORY_ADDRESS already in use by TimesTen -- file "db.c", lineno 9924, procedure "sbDbConnect"
at com.timesten.jdbc.JdbcOdbc.createSQLException(JdbcOdbc.java:3238)
at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3387)
at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3352)
at com.timesten.jdbc.JdbcOdbc.SQLDriverConnect(JdbcOdbc.java:801)
at com.timesten.jdbc.JdbcOdbcConnection.connect(JdbcOdbcConnection.java:1866)
As I has understood from the Timesten Error 8521, I have to rollback and close each direct Timesten connection in my app. I implemented the solution, but it didn't help.
My app has tho copies of a database: local and remote, and two connections to these DBs: one is direct and the second is client. The last one is used as backup for the case when the direct connection is broken.
XLA is used for monitoring data changes on the local DB.
The question is: may be these XLA subscriptions prevent the shared memory segments from being released? What should I do to avoid the error 8521 during failback?

Error while attaching to cache grid - 3399

Hi experts,
I am getting following error in cache grid operation –
3399: The recorded information indicates that there are other attached members of the grid but this member failed to communicate any of them
Let me tell you what I am trying to achieve
I have two hosts 1 and 2, host 1 and host 2 should be a part of cachegrid. Oracle DB (Persistent DB) is shared with both hosts and is at host 1. Host 2 have access to Oracle on Host 1 (I can do sqlplus from host 2 to host 1's Oracle DB)
Steps I followed are -
Host 1 – (Contains IMDB as well as Persistent DB )
call ttcacheUidPwdSet ('cacheuser','oracle');
call ttGridCreate ('Grid');
call ttGridNameSet ('Grid');
call ttcacheStart;
call ttCachePolicySet('always');
call ttrepPolicySet('always');
…some cache groups ….
call ttRepStart;
call ttGridAttach(1,'alone1','host',5001);
Host 2 - (Contain only IMDB)
call ttcacheUidPwdSet ('cacheuser','oracle');
call ttGridNameSet ('Grid');
call ttcacheStart;
call ttCachePolicySet('always');
call ttrepPolicySet('always');
…. Same cache groups as in host 1 …
call ttRepStart;
call ttGridAttach(1,'alone2','host2',5002);
ttGridNodeStatus displays on both hosts, TimesTen standalone DB attached on grid -
Command> call ttGridNodeStatus;
< GRID, 1, 1, T, host1, GRID_alone1_1, "some IP address", 5001, <NULL>, <NULL>, <NULL>, <NULL>, <NULL> >
When I try to attach host 2 on grid gets following message –
Command> call ttGridAttach(1,'alone2','host2',5002);
3399: The recorded information indicates that there are other attached members of the grid but this member failed to communicate any of them
The command failed.
All .ini files for timesten seem to be good.
Are steps correct? Did I miss something in documentation?

Hi,
The error indicates that host2 couldn't communicate with the attached data store on host1. Can you try to get more information?
1. ttStatus output of the attached data store on host1.
2. On host2, can you try to ping "some IP address"?
Besides, I noticed some inconsistency in your script. When you were attaching the first data store, you invoked:
call ttGridAttach(1,'alone1','*host*',5001);
But ttGridNodeStatus showed "*host1*" instead of "*host*".
Command> call ttGridNodeStatus;
< GRID, 1, 1, T, host1, GRID_alone1_1, "some IP address", 5001, <NULL>, <NULL>, <NULL>, <NULL>, <NULL> >
Andy

TimesTen Release 11.2.1.8.0 (32 bit Linux/x86): PLSQL_MEMORY_ADDRESS

Hi!
I am trying to setup TT 11.2.1.8.0 (32 bit Linux/x86) with jboss-4.2.3.GA using JRockit JVM. The problem I get is:
TT8517: Cannot attach PL/SQL shared memory; PLSQL_MEMORY_ADDRESS not valid or already in use -- file "db.c", lineno 9856, procedure "sbDbConnect")
I am aware of this issue with jrockit and as in http://docs.oracle.com/cd/E11882_01/timesten.112/e13080.pdf:
JRockit on 32-bit Linux allocates a default heap that is 50 percent of available
physical memory up to 1 gigabyte. Users of JRockit on 32-bit platforms may need
to choose a value for PLSQL_MEMORY_ADDRESS other than the default
+(10000000). Consider values such as B0000000, which ensures that the PL/SQL+
shared memory is not part of the JRockit heap.
So I added to sys.odbc.ini the following line:
PLSQL_MEMORY_ADDRESS=B0000000
and also in jdbc url same line. I still get:
[STDERR] org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory ([TimesTen][TimesTen 11.2.1.8.0 ODBC Driver][TimesTen]TT8517: Cannot attach PL/SQL shared memory; PLSQL_MEMORY_ADDRESS not valid or already in use -- file "db.c", lineno 9
In ttmesg.log I found corresponding log:
22:30:57.67 Info: : 2272: maind got #14.15, hello: pid=3031 type=library payload=%00%00%00%00 protocolID=TimesTen 11.2.1.8.0.tt1121 ident=%00%00%00%00
22:30:57.67 Info: : 2272: Got hello from pid 3031, type library (/usr/jrockit/bin/java -Dprogram.name=run.sh -Xms512M -Xmx512M -Djava.net.preferIPv4Stack=true -Dimsc.harmiport=3444 -Dimsc.jvmid=1 -Dimsc.configurationdir=/var/lib/OC/imsc/server/imsc-1/conf -Dimsc.jgroups.address=224.0.0.37 -Dimsc.jgroups.port=45678 -Djb)
From pmap 3031 it seems that 0xB0000000 should be free or I miscalculated it?
$ pmap 3031
3031: /usr/jrockit/bin/java -Dprogram.name=run.sh -Xms512M -Xmx512M -Djava.net.preferIPv4Stack=true -Dimsc.harmiport=3444 -Dimsc.jvmid=1 -Dimsc.configurationdir=/var/lib/OC/imsc/server/imsc-1/conf -Dimsc.jgroups.address=224.0.0.37 -Dimsc.jgroups.port=45678 -Djboss.partition.udpGroup=226.168.121.220 -jrockit -Xbootclasspath/p: -XXaggressive -XXcompaction:heapParts=512 -XXgcThreads:2 -XXgctrigger:35 -Xgc:genconcon -XXcompaction:internalPercentage=3.9 -XXcompaction:externalPercentage=3.9 -XX:+FlightRecorder -XX:Fli
08048000 64K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/bin/java
08058000 4K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/bin/java
08e5c000 38124K rwx-- [ anon ]
83b4d000 272K rwx-- [ anon ]
83b91000 84K r-x-- /usr/lib/libelf-0.137.so
83ba6000 8K rwx-- /usr/lib/libelf-0.137.so
83ba8000 31020K r-x-- /opt/TimesTen/tt1121/lib/libttpl.so
859f3000 1044K rwx-- /opt/TimesTen/tt1121/lib/libttpl.so
85af8000 64K rwx-- [ anon ]
85b08000 10812K r-x-- /opt/TimesTen/tt1121/lib/libtten.so
86597000 212K rwx-- /opt/TimesTen/tt1121/lib/libtten.so
865cc000 408K rwx-- [ anon ]
86632000 824K x [ anon ]
86716000 88K r-x-- /opt/TimesTen/tt1121/lib/libttJdbc.so
8672c000 8K rwx-- /opt/TimesTen/tt1121/lib/libttJdbc.so
8672e000 264K rwx-- [ anon ]
86770000 12K x [ anon ]
86773000 508K rwx-- [ anon ]
867f2000 12K x [ anon ]
867f5000 636K rwx-- [ anon ]
86894000 12K x [ anon ]
86897000 124K rwx-- [ anon ]
868b6000 12K x [ anon ]
868b9000 124K rwx-- [ anon ]
868d8000 12K x [ anon ]
868db000 124K rwx-- [ anon ]
868fa000 12K x [ anon ]
868fd000 124K rwx-- [ anon ]
8691c000 12K x [ anon ]
8691f000 124K rwx-- [ anon ]
8693e000 12K x [ anon ]
86941000 508K rwx-- [ anon ]
869c0000 12K x [ anon ]
869c3000 516K rwx-- [ anon ]
86a44000 12K x [ anon ]
86a47000 124K rwx-- [ anon ]
86a66000 12K x [ anon ]
86a69000 380K rwx-- [ anon ]
86ac8000 12K x [ anon ]
86acb000 260K rwx-- [ anon ]
86b0c000 12K x [ anon ]
86b0f000 508K rwx-- [ anon ]
86b8e000 12K x [ anon ]
86b91000 380K rwx-- [ anon ]
86bf0000 12K x [ anon ]
86bf3000 116K rwx-- [ anon ]
86c10000 2932K rwxs- [ shmid=0x6000b ]
86eed000 1420K rwx-- [ anon ]
87050000 12K x [ anon ]
87053000 948K rwx-- [ anon ]
87140000 1024K rwxs- /var/lib/OC/imsc/server/imsc-1/data/hypersonic/localDB.data
87240000 1768K rwx-- [ anon ]
873fa000 24K x [ anon ]
8740b000 8K rwx-- [ anon ]
8740d000 12K x [ anon ]
87410000 508K rwx-- [ anon ]
8748f000 12K x [ anon ]
87492000 4028K rwx-- [ anon ]
87881000 12K x [ anon ]
87884000 124K rwx-- [ anon ]
878a3000 12K x [ anon ]
878a6000 124K rwx-- [ anon ]
878c5000 12K x [ anon ]
878c8000 124K rwx-- [ anon ]
878e7000 12K x [ anon ]
878ea000 124K rwx-- [ anon ]
87909000 12K x [ anon ]
8790c000 124K rwx-- [ anon ]
8792b000 12K x [ anon ]
8792e000 124K rwx-- [ anon ]
8794d000 12K x [ anon ]
87950000 124K rwx-- [ anon ]
8796f000 12K x [ anon ]
87972000 124K rwx-- [ anon ]
87991000 12K x [ anon ]
87994000 124K rwx-- [ anon ]
879b3000 12K x [ anon ]
879b6000 124K rwx-- [ anon ]
879d5000 12K x [ anon ]
879d8000 380K rwx-- [ anon ]
87a37000 12K x [ anon ]
87a3a000 124K rwx-- [ anon ]
87a59000 12K x [ anon ]
87a5c000 116K rwx-- [ anon ]
87a79000 4K x [ anon ]
87a7a000 10240K rwx-- [ anon ]
8847a000 4K x [ anon ]
8847b000 13840K rwx-- [ anon ]
891ff000 4K x [ anon ]
89207000 648K rwx-- [ anon ]
892a9000 12K x [ anon ]
892ac000 3196K rwx-- [ anon ]
895cb000 4K x [ anon ]
895cc000 10240K rwx-- [ anon ]
89fcc000 4K x [ anon ]
89fcd000 10240K rwx-- [ anon ]
8a9cd000 4K x [ anon ]
8a9ce000 10240K rwx-- [ anon ]
8b3ce000 4K x [ anon ]
8b3cf000 10240K rwx-- [ anon ]
8bdcf000 4K x [ anon ]
8bdd0000 10240K rwx-- [ anon ]
8c7de000 8K rwx-- [ anon ]
8c7e0000 12K x [ anon ]
8c7e3000 116K rwx-- [ anon ]
8c800000 36K r-x-- /lib/libcrypt-2.5.so
8c809000 4K r-x-- /lib/libcrypt-2.5.so
8c80a000 4K rwx-- /lib/libcrypt-2.5.so
8c80b000 156K rwx-- [ anon ]
8c832000 56K r-x-- /opt/OC/lib/libfmkmgrts.so.4.2.10
8c840000 4K rwx-- /opt/OC/lib/libfmkmgrts.so.4.2.10
8c841000 8K rwx-- [ anon ]
8c843000 448K r-x-- /opt/OC/lib/libfmkmgt.so.4.2.10
8c8b3000 16K rwx-- /opt/OC/lib/libfmkmgt.so.4.2.10
8c8b7000 228K r-x-- /opt/OC/lib/liboclic_core.so.0.0.1
8c8f0000 8K rwx-- /opt/OC/lib/liboclic_core.so.0.0.1
8c8f2000 92K r-x-- /opt/OC/lib/liboclic.so.0.0.1
8c909000 4K rwx-- /opt/OC/lib/liboclic.so.0.0.1
8c90a000 2352K r-x-- /opt/OC/lib/libocsipcore.so.1.4.4
8cb56000 8K rwx-- /opt/OC/lib/libocsipcore.so.1.4.4
8cb58000 8K rwx-- [ anon ]
8cb5a000 324K r-x-- /opt/OC/lib/libocsipmsg.so.1.4.4
8cbab000 8K rwx-- /opt/OC/lib/libocsipmsg.so.1.4.4
8cbad000 300K r-x-- /opt/OC/lib/java/libocsipjni.so.1.4.4
8cbf8000 4K rwx-- /opt/OC/lib/java/libocsipjni.so.1.4.4
8cbf9000 256K rwx-- [ anon ]
8cc39000 4K x [ anon ]
8cc3a000 10240K rwx-- [ anon ]
8d63a000 4K x [ anon ]
8d63b000 10240K rwx-- [ anon ]
8e03b000 4K x [ anon ]
8e03c000 10240K rwx-- [ anon ]
8ea3c000 4K x [ anon ]
8ea3d000 10240K rwx-- [ anon ]
8f43d000 4K x [ anon ]
8f43e000 10240K rwx-- [ anon ]
8fe3e000 4K x [ anon ]
8fe3f000 10240K rwx-- [ anon ]
9083f000 4K x [ anon ]
90840000 10240K rwx-- [ anon ]
91240000 40K r-x-- /opt/OC/lib/libTTLBase.so.1.0.0
9124a000 4K rwx-- /opt/OC/lib/libTTLBase.so.1.0.0
9124b000 120K rwx-- [ anon ]
91269000 36K r-x-- /opt/OC/lib/libTTL.so.1.0.0
91272000 28K rwx-- /opt/OC/lib/libTTL.so.1.0.0
91279000 4K rwx-- [ anon ]
9127a000 236K r-x-- /lib/libsepol.so.1
912b5000 4K rwx-- /lib/libsepol.so.1
912b6000 40K rwx-- [ anon ]
912c0000 88K r-x-- /lib/libselinux.so.1
912d6000 8K rwx-- /lib/libselinux.so.1
912d8000 176K r-x-- /usr/lib/libgssapi_krb5.so.2.2
91304000 4K rwx-- /usr/lib/libgssapi_krb5.so.2.2
91305000 148K r-x-- /usr/lib/libk5crypto.so.3.1
9132a000 4K rwx-- /usr/lib/libk5crypto.so.3.1
9132b000 588K r-x-- /usr/lib/libkrb5.so.3.3
913be000 12K rwx-- /usr/lib/libkrb5.so.3.3
913c1000 72K r-x-- /usr/lib/libz.so.1.2.3
913d3000 4K rwx-- /usr/lib/libz.so.1.2.3
913d4000 1192K r-x-- /lib/libcrypto.so.0.9.8e
914fe000 76K rwx-- /lib/libcrypto.so.0.9.8e
91511000 16K rwx-- [ anon ]
91515000 268K r-x-- /lib/libssl.so.0.9.8e
91558000 16K rwx-- /lib/libssl.so.0.9.8e
9155c000 888K r-x-- /usr/lib/libstdc++.so.6.0.8
9163a000 12K r-x-- /usr/lib/libstdc++.so.6.0.8
9163d000 8K rwx-- /usr/lib/libstdc++.so.6.0.8
9163f000 152K rwx-- [ anon ]
91667000 180K r-x-- /opt/OC/lib/libfmkgmp.so.4.2.10
91694000 4K rwx-- /opt/OC/lib/libfmkgmp.so.4.2.10
91695000 100K r-x-- /opt/OC/lib/libfmkmgr.so.4.2.10
916ae000 4K rwx-- /opt/OC/lib/libfmkmgr.so.4.2.10
916af000 212K r-x-- /opt/OC/lib/libfmkbus.so.4.9.2
916e4000 4K rwx-- /opt/OC/lib/libfmkbus.so.4.9.2
916e5000 32K rwx-- [ anon ]
916ed000 224K r-x-- /opt/OC/lib/libfmktbx.so.4.8.8
91725000 12K rwx-- /opt/OC/lib/libfmktbx.so.4.8.8
91728000 100K rwx-- [ anon ]
91741000 12K x [ anon ]
91744000 124K rwx-- [ anon ]
91763000 12K x [ anon ]
91766000 124K rwx-- [ anon ]
91785000 12K x [ anon ]
91788000 180K rwx-- [ anon ]
917c1000 8K rwx-- [ anon ]
917c3000 12K x [ anon ]
917c6000 124K rwx-- [ anon ]
917e5000 12K x [ anon ]
917e8000 124K rwx-- [ anon ]
91807000 12K x [ anon ]
9180a000 124K rwx-- [ anon ]
91829000 12K x [ anon ]
9182c000 124K rwx-- [ anon ]
9184b000 12K x [ anon ]
9184e000 124K rwx-- [ anon ]
9186d000 12K x [ anon ]
91870000 124K rwx-- [ anon ]
9188f000 12K x [ anon ]
91892000 124K rwx-- [ anon ]
918b1000 12K x [ anon ]
918b4000 124K rwx-- [ anon ]
918d3000 12K x [ anon ]
918d6000 124K rwx-- [ anon ]
918f5000 12K x [ anon ]
918f8000 116K rwx-- [ anon ]
91915000 2932K rwxs- [ shmid=0x50009 ]
91bf2000 1028K rwx-- [ anon ]
91cf3000 2932K rwxs- [ shmid=0x48008 ]
91fd0000 64K rwx-- [ anon ]
91fee000 8K rwx-- [ anon ]
91ff0000 12K x [ anon ]
91ff3000 116K rwx-- [ anon ]
9201e000 8K rwx-- [ anon ]
92020000 12K x [ anon ]
92023000 244K rwx-- [ anon ]
9206a000 648K rwx-- [ anon ]
9210c000 12K x [ anon ]
9210f000 124K rwx-- [ anon ]
9212e000 12K x [ anon ]
92131000 124K rwx-- [ anon ]
92150000 12K x [ anon ]
92153000 692K rwx-- [ anon ]
9220a000 1156K rwx-- [ anon ]
9232b000 200K r-x-- /opt/OC/lib/java/libSaNtfJava.so.1.0.0
9235d000 4K rwx-- /opt/OC/lib/java/libSaNtfJava.so.1.0.0
9235e000 264K rwx-- [ anon ]
923a0000 12K x [ anon ]
923a3000 1360K rwx-- [ anon ]
924f7000 36K x [ anon ]
9250e000 2816K rwx-- [ anon ]
927d9000 60K r-x-- /lib/libresolv-2.5.so
927e8000 4K r-x-- /lib/libresolv-2.5.so
927e9000 4K rwx-- /lib/libresolv-2.5.so
927ea000 16K rwx-- [ anon ]
927ee000 12K x [ anon ]
927f1000 628K rwx-- [ anon ]
9289c000 8K rwx-- [ anon ]
9289e000 12K x [ anon ]
928a1000 1916K rwx-- [ anon ]
92a80000 12K x [ anon ]
92a83000 3188K rwx-- [ anon ]
92dae000 8K rwx-- [ anon ]
92db0000 12K x [ anon ]
92db3000 380K rwx-- [ anon ]
92e12000 12K x [ anon ]
92e15000 124K rwx-- [ anon ]
92e34000 12K x [ anon ]
92e37000 124K rwx-- [ anon ]
92e56000 12K x [ anon ]
92e59000 124K rwx-- [ anon ]
92e78000 12K x [ anon ]
92e7b000 124K rwx-- [ anon ]
92e9a000 12K x [ anon ]
92e9d000 124K rwx-- [ anon ]
92ebc000 12K x [ anon ]
92ebf000 124K rwx-- [ anon ]
92ede000 12K x [ anon ]
92ee1000 124K rwx-- [ anon ]
92f00000 12K x [ anon ]
92f03000 124K rwx-- [ anon ]
92f22000 12K x [ anon ]
92f25000 124K rwx-- [ anon ]
92f44000 12K x [ anon ]
92f47000 124K rwx-- [ anon ]
92f66000 12K x [ anon ]
92f69000 124K rwx-- [ anon ]
92f88000 12K x [ anon ]
92f8b000 124K rwx-- [ anon ]
92faa000 12K x [ anon ]
92fad000 124K rwx-- [ anon ]
92fcc000 12K x [ anon ]
92fcf000 124K rwx-- [ anon ]
92fee000 12K x [ anon ]
92ff1000 124K rwx-- [ anon ]
93010000 12K x [ anon ]
93013000 380K rwx-- [ anon ]
93072000 12K x [ anon ]
93075000 636K rwx-- [ anon ]
93114000 12K x [ anon ]
93117000 124K rwx-- [ anon ]
93136000 12K x [ anon ]
93139000 124K rwx-- [ anon ]
93158000 12K x [ anon ]
9315b000 124K rwx-- [ anon ]
9317a000 12K x [ anon ]
9317d000 124K rwx-- [ anon ]
9319c000 12K x [ anon ]
9319f000 124K rwx-- [ anon ]
931be000 12K x [ anon ]
931c1000 124K rwx-- [ anon ]
931e0000 12K x [ anon ]
931e3000 124K rwx-- [ anon ]
93202000 12K x [ anon ]
93205000 124K rwx-- [ anon ]
93224000 12K x [ anon ]
93227000 124K rwx-- [ anon ]
93246000 12K x [ anon ]
93249000 380K rwx-- [ anon ]
932a8000 12K x [ anon ]
932ab000 884K rwx-- [ anon ]
93397000 124K r-x-- /lib/libexpat.so.0.5.0
933b6000 8K rwx-- /lib/libexpat.so.0.5.0
933b8000 1672K rwx-- [ anon ]
9355a000 12K x [ anon ]
9355d000 124K rwx-- [ anon ]
9357c000 12K x [ anon ]
9357f000 124K rwx-- [ anon ]
9359e000 12K x [ anon ]
935a1000 124K rwx-- [ anon ]
935c0000 12K x [ anon ]
935c3000 124K rwx-- [ anon ]
935e2000 12K x [ anon ]
935e5000 124K rwx-- [ anon ]
93604000 12K x [ anon ]
93607000 124K rwx-- [ anon ]
93626000 12K x [ anon ]
93629000 372K rwx-- [ anon ]
9368c000 100K r-x-- /opt/OC/lib/libSaNtf.so.1.0.0
936a5000 4K rwx-- /opt/OC/lib/libSaNtf.so.1.0.0
936a6000 64K rwx-- [ anon ]
936b6000 44K r-x-- /lib/libgcc_s-4.1.2-20080825.so.1
936c1000 4K rwx-- /lib/libgcc_s-4.1.2-20080825.so.1
936c2000 72K rwx-- [ anon ]
936d4000 12K x [ anon ]
936d7000 764K rwx-- [ anon ]
93796000 12K x [ anon ]
93799000 3380K rwx-- [ anon ]
93aec000 32K rwxs- [ shmid=0x10001 ]
93af4000 8K rwx-- [ anon ]
93af6000 12K x [ anon ]
93af9000 756K rwx-- [ anon ]
93bb7000 32K r-x-- /usr/lib/libkrb5support.so.0.1
93bbf000 4K rwx-- /usr/lib/libkrb5support.so.0.1
93bc0000 8K rwx-- [ anon ]
93bc2000 12K x [ anon ]
93bc5000 124K rwx-- [ anon ]
93be4000 12K x [ anon ]
93be7000 124K rwx-- [ anon ]
93c06000 12K x [ anon ]
93c09000 1396K rwx-- [ anon ]
93d66000 36K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libjmapi.so
93d6f000 4K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libjmapi.so
93d74000 712K rwx-- [ anon ]
93e26000 12K x [ anon ]
93e29000 124K rwx-- [ anon ]
93e48000 12K x [ anon ]
93e4b000 124K rwx-- [ anon ]
93e6a000 12K x [ anon ]
93e6d000 124K rwx-- [ anon ]
93e8c000 12K x [ anon ]
93e8f000 124K rwx-- [ anon ]
93eae000 12K x [ anon ]
93eb1000 380K rwx-- [ anon ]
93f10000 12K x [ anon ]
93f13000 124K rwx-- [ anon ]
93f32000 12K x [ anon ]
93f35000 124K rwx-- [ anon ]
93f54000 12K x [ anon ]
93f57000 1020K rwx-- [ anon ]
94056000 12K x [ anon ]
94059000 124K rwx-- [ anon ]
94078000 12K x [ anon ]
9407b000 124K rwx-- [ anon ]
9409a000 12K x [ anon ]
9409d000 124K rwx-- [ anon ]
940bc000 12K x [ anon ]
940bf000 380K rwx-- [ anon ]
9411e000 12K x [ anon ]
94121000 124K rwx-- [ anon ]
94140000 12K x [ anon ]
94143000 1972K rwx-- [ anon ]
94331000 64K r-x-- /usr/lib/liblog4c.so.3.1.0
94341000 4K rwx-- /usr/lib/liblog4c.so.3.1.0
94342000 68K rwx-- [ anon ]
94359000 4K r-x-- /usr/lib/libaio.so.1.0.1
9435a000 4K rwx-- /usr/lib/libaio.so.1.0.1
9435b000 28K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libnio.so
94362000 4K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libnio.so
94363000 264K rwx-- [ anon ]
943a5000 12K x [ anon ]
943a8000 4156K rwx-- [ anon ]
947b7000 12K x [ anon ]
947ba000 828K rwx-- [ anon ]
94889000 12K x [ anon ]
9488c000 884K rwx-- [ anon ]
94969000 24K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/liborii.so
9496f000 4K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/liborii.so
94970000 3448K rwx-- [ anon ]
94cce000 200K x [ anon ]
94d01000 16K r-x-- /opt/OC/lib/libntl.so.1.0.0
94d05000 4K rwx-- /opt/OC/lib/libntl.so.1.0.0
94d06000 80K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libnet.so
94d1a000 4K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libnet.so
94d1b000 24K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libmanagement.so
94d21000 4K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libmanagement.so
94d22000 8K rwx-- [ anon ]
94d24000 12K x [ anon ]
94d27000 116K rwx-- [ anon ]
94d44000 8K r-x-- /usr/lib/libsctp.so.1.0.6
94d46000 4K rwx-- /usr/lib/libsctp.so.1.0.6
94d47000 12K r-x-- /opt/OC/lib/libiniparser.so.1.0.0
94d4a000 4K rwx-- /opt/OC/lib/libiniparser.so.1.0.0
94d4b000 24K r-x-- /usr/lib/openais/libSaEvt.so.2.0.0
94d51000 4K rwx-- /usr/lib/openais/libSaEvt.so.2.0.0
94d52000 8K rwx-- [ anon ]
94d54000 12K x [ anon ]
94d57000 1212K rwx-- [ anon ]
94e86000 12K x [ anon ]
94e89000 124K rwx-- [ anon ]
94ea8000 12K x [ anon ]
94eab000 252K rwx-- [ anon ]
94eea000 12K x [ anon ]
94eed000 124K rwx-- [ anon ]
94f0c000 12K x [ anon ]
94f0f000 124K rwx-- [ anon ]
94f2e000 12K x [ anon ]
94f31000 124K rwx-- [ anon ]
94f50000 12K x [ anon ]
94f53000 252K rwx-- [ anon ]
94f92000 12K x [ anon ]
94f95000 252K rwx-- [ anon ]
94fd4000 12K x [ anon ]
94fd7000 884K rwx-- [ anon ]
950b4000 60K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libzip.so
950c3000 8K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libzip.so
950c5000 520K rwx-- [ anon ]
95147000 12K x [ anon ]
9514a000 124K rwx-- [ anon ]
95169000 12K x [ anon ]
9516c000 124K rwx-- [ anon ]
9518b000 12K x [ anon ]
9518e000 252K rwx-- [ anon ]
951cd000 12K x [ anon ]
951d0000 244K rwx-- [ anon ]
9520d000 24K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/native_threads/libhpi.so
95213000 4K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/native_threads/libhpi.so
95214000 384K rwx-- [ anon ]
95274000 76K r-x-- /lib/libnsl-2.5.so
95287000 4K r-x-- /lib/libnsl-2.5.so
95288000 4K rwx-- /lib/libnsl-2.5.so
95289000 8K rwx-- [ anon ]
9528c000 4K rwx-- [ anon ]
9528d000 8K r-x-- /lib/libkeyutils-1.2.so
9528f000 4K rwx-- /lib/libkeyutils-1.2.so
95290000 8K r-x-- /lib/libcom_err.so.2.1
95292000 4K rwx-- /lib/libcom_err.so.2.1
95293000 20K r-x-- /opt/OC/lib/java/libgmfjni.so.4.2.10
95298000 4K rwx-- /opt/OC/lib/java/libgmfjni.so.4.2.10
95299000 140K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libjava.so
952bc000 8K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libjava.so
952be000 44K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libverify.so
952c9000 4K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libverify.so
952ca000 552764K rwx-- [ anon ]
b6e99000 52K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libjfr.so
b6ea6000 4K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libjfr.so
b6ea7000 636K rwx-- [ anon ]
b6f46000 36K r-x-- /lib/libnss_files-2.5.so
b6f4f000 4K r-x-- /lib/libnss_files-2.5.so
b6f50000 4K rwx-- /lib/libnss_files-2.5.so
b6f51000 1024K rwx-- [ anon ]
b7051000 4K x [ anon ]
b7052000 4K rwx-- [ anon ]
b7053000 12K x [ anon ]
b7056000 10224K rwx-- [ anon ]
b7a52000 28K r-x-- /lib/librt-2.5.so
b7a59000 4K r-x-- /lib/librt-2.5.so
b7a5a000 4K rwx-- /lib/librt-2.5.so
b7a5b000 148K r-x-- /lib/libm-2.5.so
b7a80000 4K r-x-- /lib/libm-2.5.so
b7a81000 4K rwx-- /lib/libm-2.5.so
b7a82000 4K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/librmi.so
b7a83000 4K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/librmi.so
b7a84000 4K r-x-- /opt/OC/lib/java/hpoc-fsc-core/ocsac-starter-ext.so.1.0.0
b7a85000 4K rwx-- /opt/OC/lib/java/hpoc-fsc-core/ocsac-starter-ext.so.1.0.0
b7a86000 4K r-x-- [ anon ]
b7a87000 4K rwx-- [ anon ]
b7a88000 32K rwxs- /tmp/hsperfdata_ocadmin/3031
b7a90000 108K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libosal.so
b7aab000 4K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libosal.so
b7aac000 4K rwx-- [ anon ]
b7aad000 2828K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/jrockit/libjvm.so
b7d70000 108K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/jrockit/libjvm.so
b7d8b000 368K rwx-- [ anon ]
b7de7000 1276K r-x-- /lib/libc-2.5.so
b7f26000 4K x /lib/libc-2.5.so
b7f27000 8K r-x-- /lib/libc-2.5.so
b7f29000 4K rwx-- /lib/libc-2.5.so
b7f2a000 12K rwx-- [ anon ]
b7f2d000 76K r-x-- /lib/libpthread-2.5.so
b7f40000 4K r-x-- /lib/libpthread-2.5.so
b7f41000 4K rwx-- /lib/libpthread-2.5.so
b7f42000 8K rwx-- [ anon ]
b7f44000 8K r-x-- /lib/libdl-2.5.so
b7f46000 4K r-x-- /lib/libdl-2.5.so
b7f47000 4K rwx-- /lib/libdl-2.5.so
b7f48000 4K r-x-- /opt/OC/lib/java/hpoc-fsc-core/ocsac-starter.so.1.0.0
b7f49000 4K rwx-- /opt/OC/lib/java/hpoc-fsc-core/ocsac-starter.so.1.0.0
b7f4a000 44K r-x-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libutil.so
b7f55000 4K rwx-- /usr/java/jrockit-jdk1.6.0_26-R28.1.4-4.0.1.orig/jre/lib/i386/libutil.so
b7f56000 4K rwx-- [ anon ]
b7f57000 4K r-x-- [ anon ]
b7f58000 104K r-x-- /lib/ld-2.5.so
b7f72000 4K r-x-- /lib/ld-2.5.so
b7f73000 4K rwx-- /lib/ld-2.5.so
bfd4d000 84K rwx-- [ stack ]
total 893656K
Please help,
Ivan

I was wrong - my choosen memory address was already used :-(.
Now I decided to use 0xb9000000 which is free. What I get on JDBC side is:
[STDERR] Caused by: java.sql.SQLException: [TimesTen][TimesTen 11.2.1.8.0 ODBC Driver][TimesTen]TT15019: Only the instance admin may alter the PLSQL_MEMORY_ADDRESS attribute -- file "db.c", lineno 9722, procedure "sbDbConnect"
and in ttmesg:
22:52:44.39 Info: : 2281: 8892 0x85ace688: Connect /opt/TimesTen/tt1121/occpdb_datastore/occpdb_1121 a=0x0 f=0x1000040
22:52:44.39 Info: : 2281: permsize=41943040 tempsize=33554432
22:52:44.39 Info: : 2281: logbuffersize=0 logfilesize=0
22:52:44.39 Info: : 2281: permwarnthresh=90 tempwarnthresh=90 logflushmethod=0 connections=0
22:52:44.39 Info: : 2281: ckptfrequency=-1 ckptlogvolume=-1 conn_name=java
22:52:44.39 Info: : 2281: recoverythreads=0 logbufparallelism=0
22:52:44.39 Info: : 2281: plsql=1 sgasize=33554432 sgaaddr=0xb9000000
22:52:44.39 Info: : 2281: control1=0 control2=0 control3=0
22:52:44.39 Info: : 2281: ckptrate=-1 receiverThreads=0
22:52:44.39 Info: : 2281: cacheAwtMethod=0
22:52:44.39 Info: : 2281: 2281/8892: <wait and mark>: Mark in-flux (now reason 2=connect pid 8892 nwaiters 0 ds /opt/TimesTen/tt1121/occpdb_datastore/occpdb_1121) (was reason 0)
22:52:44.39 Info: : 2281: Marked in flux for connect by 8892 : 0
22:52:44.39 Info: : 2281: daDbConnect failed
22:52:44.39 Info: : 2281: connect.c:1928: Mark not in-flux (was reason 2=connect pid 8892 nwaiters 0 ds /opt/TimesTen/tt1121/occpdb_datastore/occpdb_1121)
22:52:44.39 Info: : 2281: return 1 15019 'illegal request to change 1st connect attribute' arg1='PLSQL_MEMORY_ADDRESS' arg1type='S' arg2='' arg2type='S'
22:52:44.39 Info: : 2281: maind: done with request #15.18
The PLSQL_MEMORY_ADDRESS is set in sys.odbc.ini:
[occpdb_1121]
Driver=/opt/TimesTen/tt1121/lib/libtten.so
ConnectionCharacterSet=US7ASCII
DatabaseCharacterSet=US7ASCII
DataStore=/opt/TimesTen/tt1121/occpdb_datastore/occpdb_1121
PermSize=40
TempSize=32
PLSQL_MEMORY_ADDRESS=B9000000
PLSQL=1
How to make this work?
Please advise,
Ivan

Phone requesting to be restored but can't unlock!

My phone lost coverege became stuck on the apple icon screen, then a few hrs later requested that it be restored and attached to iTunes in order to do this.BUT.... my laptop can't communicate with it as it tells me that the phone is locked by a pin code (which it is) but there is no pincode screen on the phone to unlock it! So I am stuck with a phone requesting to be restored and a laptop requesting that i unlock the phone.....and a phone that won't give me the option of unlocking it. Any ideas?

Try recovery mode.
<http://support.apple.com/kb/ht1808>

Attached database failed for sever "blah". (Microsoft.SqlServer.Smo)

===================================
Attach database failed for Server 'DENR-HP'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1539+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
Program Location:
at Microsoft.SqlServer.Management.Smo.Server.AttachDatabase(String name, StringCollection files)
at Microsoft.SqlServer.Management.SqlManagerUI.AttachDatabaseData.PrimaryFile.Attach()
at Microsoft.SqlServer.Management.SqlManagerUI.AttachDatabase.SendDataToServer()
===================================
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Program Location:
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(StringCollection sqlCommands, ExecutionTypes executionType)
at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(StringCollection queries)
at Microsoft.SqlServer.Management.Smo.Server.AttachDatabaseWorker(String name, StringCollection files, String owner, AttachOptions attachOptions)
at Microsoft.SqlServer.Management.Smo.Server.AttachDatabase(String name, StringCollection files)
===================================
The database 'PlanningDB' cannot be opened because it is version 655. This server supports version 611 and earlier. A downgrade path is not supported.
Could not open new database 'PlanningDB'. CREATE DATABASE is aborted. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=948&LinkId=20476
Server Name: (local)
Error Number: 948
Severity: 20
State: 1
Line Number: 1
Program Location:
at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)

Hi,
As Olaf’s post, you cannot restore or attach a database which is created from a higher version of SQL Server to a lower version of SQL Server.
However, there are some ways which can help you to move a database to a lower version of SQL Server. I recommend you to use Generate Scripts Wizard of SQL Server Management Studio (SSMS), you can script all the database objects in SQL Server 2008, then run
the SQL scripts in SQL Server 2005, for more details, you can follow the steps in this blog:
How to migrate a SQL Server database to a lower version. Also you can try to use the Import and Export Wizard to move database from SQL Server 2008 to SQL Server 2005,for more details, please review this article:
How to: Run the SQL Server Import and Export Wizard.
Thanks
Lydia Zhang

Cannot attach data store shared-memory segment using JDBC (TT0837) 11.2.1.5

Hi,
I found the thread Cannot attach data store shared-memory segment using JDBC (TT0837) but it can't help me out.
I encounter this issue in Windows XP, and application gets connection from jboss data source.
url=jdbc:timesten:direct:dsn=test;uid=test;pwd=test;OraclePWD=test
username=test
password=test
Error information:
java.sql.SQLException: [TimesTen][TimesTen 11.2.1.5.0 ODBC Driver][TimesTen]TT0837: Cannot attach data store
shared-memory segment, error 8 -- file "db.c", lineno 9818, procedure "sbDbConnect"
at com.timesten.jdbc.JdbcOdbc.createSQLException(JdbcOdbc.java:3295)
at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3444)
at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3409)
at com.timesten.jdbc.JdbcOdbc.SQLDriverConnect(JdbcOdbc.java:813)
at com.timesten.jdbc.JdbcOdbcConnection.connect(JdbcOdbcConnection.java:1807)
at com.timesten.jdbc.TimesTenDriver.connect(TimesTenDriver.java:303)
at com.timesten.jdbc.TimesTenDriver.connect(TimesTenDriver.java:159)
I am confused that if I use jdbc, there is no such error.
Connection conn = DriverManager.getConnection("url", "username", "password");
Regards,
Nesta

I think error 8 is
net helpmsg 8
Not enough storage is available to process this command.
If I'm wrong I'm happy to be corrected. If you reduce the PermSize and TempSize of the datastore (just as a test) does this allow JBOSS to load it?
You don't say whether this is 32bit or 64bit Windows. If it's the former, the following information may be helpful.
"Windows manages virtual memory differently than all other OSes. The way Windows sets up memory for DLLs guarantees that the virtual address space of each process is badly fragmented. Other OSes avoid this by densely packing shared libraries.
A TimesTen database is represented as a single contiguous shared segment. So for an application to connect to a database of size n, there must be n bytes of unused contiguous virtual memory in the application's process. Because of the way Windows manages DLLs this is sometimes challenging. You can easily get into a situation where simple applications that use few DLLs (such as ttIsql) can access a database fine, but complicated apps that use many DLLs can not.
As a practical matter this means that TimesTen direct-mode in Windows 32-bit is challenging to use for those with complex applications. For large C/C++ applications one can usually "rebase" DLLs to reduce fragmentation. But for Java based applications this is more challenging.
You can use tools like the free "Process Explorer" to see the used address ranges in your process.
Naturally, 64-bit Windows basically resolves these issues by providing a dramatically larger set of addresses."

TimesTen and Eclipse java development problem

Hello all
Using TimesTen with JDBC in from a Java code developed on Eclipse I encounter a problem: when running the program in debug mode, everything works fine. Running without debug, or outside Eclipse, results in the following error:
java.sql.SQLException: [TimesTen][TimesTen 7.0.5.0.0 ODBC Driver][TimesTen]TT0837: Cannot attach data store shared-memory segment, error 8 -- file "db.c", lineno 7891, procedure "sbDbCreate"
Does anyone know the cause of this, or can point me to logs or other resources I can look into?
Regards,
Shaul Peled
Nuance Communication Inc.

Okay, it is almost certainly an address space issue. Unfortunately 32-bit Windows is about the most problematic platform from this perspective. A TimesTen datastore is a single, contiguous memory region of size approximating PermSize+TempSize+LogBuffSize+DS header. In your case that will be about 1098 Mb. To 'connect' to this datastore, it is necessary to map the datastore memory (it is a shared mapping allocated from the Windows paging file) into your process (in this case the JVM) as a single region. Unfortunately, unlike most O/S, in Windows shared libraries (DLLs) have to be loaded at fixed locations in the address space defined when the DLL was linked. This means that although your process has a 4 GB address space (with quite a bit reserved for WIndows and other uses) that space is often highly fragmented with various DLLs (system and application) located all over the place. This means that often it is hard to find a single contiguous address space region to map a large datastore.
into.
To verify that this is the issue, could you try reducing the datastore size to say PermSize=128, TempSize=64 and see if you can connect then. If you can then you will have to experiment by slowly increasing Perm and Temp until you find the maximum size store you can accomodate. If you are using no logging (Are you sure that is what you want? You will end up with a single threaded datastore if you do that...) you could reduce LogBuffSize to the smallest allowed value (128 Kb).
If it does turn out to be an address space issue then you have 3 options:
1. Live with a smaller datastore size.
2. Try and re-arrange the memory map by rebasing DLLs to create a larger contiguous region. Note that ijn any event it is very unlikely you will ever be able to exceed ~1.5 Gb for a datastore.
3. Switch to 64-bit Windows, 64-bit TimesTen and a 64-bit JVM. Then the only limit on datastore size is available RAM.
Let me know the outcome.
Regards,
Chris

Restoring photo with severe water damage

A friend of mine asked me to restore the attached photo (of her dad) which has suffered severe water damage (I have erased the gentleman since I have not asked for permission to share the photo with others). Fortunately the person's face is intact but everything else is damaged. The peak in the background is the Matterhorn in the Swiss Alps and the photographer chose this clever angle so that the person is almost as large as the peak. I know how to use spot healing and the clone stamp but my biggest problem is that the outline of the peak has been obliterated. I tried boosting the contrast with a layer and had only limited success on the right but none on the left.
My question two-fold:
1) could you suggest a method to reveal more of the mountain outline and
2) if guessing is the only choice left, what is the best way to draw the edges of the mountain peak
In passing I mentioned to my friend the possibility of inserting her father in a stock photo of the Matterhorn but "a fake" just won't do because this photo holds very special meaning for her.
Any advice you can give me will be greatly appreciated. Thanks!

I revised my steps and added more info about the gradient. Hope this helps.
1. Add a blank layer and apply a Layers Mask to it.
2. Select the mountain.
3. Activate the mask and fill the selection with black. The mask now shows the black silhouette of the mountain.
4. Important! Delete the selection (Ctrl-D).
Now to create the sky using a gradient. The purpose of the gradient is to create a natural-looking sky ranging from light gray at the bottom to dark at the top.
5. Set the Foreground and Background color chips (at bottom of toolbar) to light and dark grey respectively. I used RGB values 220,220,220 for the Foreground, and 160,160,160 for the Background.
6. In the Gradient Editor select the Foreground to Background Preset, and on the tool options bar choose Linear Gradient.
7. Click the layer's thumbnail to activate the layer, and draw the gradient vertically upwards. Because of the mask the gradient does not cover the mountain. The degree of the light-to-dark transition depends on the gradient's start and end points, so you might have to redraw the gradient several times until it looks natural. You can redraw over the existing gradient; no need to start from scratch. In this example I drew the gradient starting from the center of the picture all the way to the top.

SQL Content Database Restore

Environment :- Sharepoint 2013
The farm already has the content database attached to a web application (web app 1)
The client needs a same content database (copy) to be restored and attached to a new web application (web app 2).
we are using the command -assignnewdatabaseid, even then we are not able to see all the site collections.
Please advise

That's expected behavior as the Site Collections have the same GUID, so the second copy (Web App 2) will not be able to see them. Your options are:
1) Restore the Content Database to a Web Application on another farm
2) Use Backup-SPSite/Restore-SPSite which assigns a new GUID to the Site Collection so you can 'duplicate' it within the same farm
3) Use a 3rd party content migration tool
4) Use Export-SPWeb/Import-SPWeb
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Backup and Restore SQL

Dear Gurus,
I have offline database backup for DATA1, DATA2 , DATA3 and LOG1 file.
Now I have one more Demo server. That server also have some Database SID.
How to detach and Attach database as well as do the work on the attach database client.
Please tell me advice.

Hello,
First get fimiliarity with ms Management Console. And using Installation master you can do backup/restore and attach/detach method, to make the other system.
Refer the following useful notes also.
SAP Note 1420452 - FAQ: Restore and recovery with MS SQL Server
SAP Note 683447 - SAP Tools for MS SQL Server, after SQL DB restore.
Note 555223 - FAQ: Microsoft SQL Server
Regards,
MSR

TimesTen restore/re-attach

Similar Messages

Maybe you are looking for