RHEL CMOD 9.5 DB - remote oracle 11g
arsload fails:
Note:
1) As per Alassandro's, suggestion in earlier post, left the ars.dbfs empty for using remote oracle.
2) Permissions granted for the oracle DB schema (id) are as defined in this link except for TABLESPACE create and drop. http://www-01.ibm.com/support/docview.wss?uid=swg21571134
from system log :
ARS0015E Unable to find SMS tablespace filesystems. Either the defined SMS filesystems are full or there are no SMS filesystems defined.
arsload trace errors:
17728:140080102217504 08/14/2016 02:10:56:152994 ERROR arsload.c(6144)ArcLOADP_LoadDB:Current state msg_id=464
17728:140080102217504 08/14/2016 02:10:56:153014 ERROR arsload.c(6151)ArcLOADP_LoadDB:Current state msg_id=511
17728:140080102217504 08/14/2016 02:10:56:153124 ERROR arsload.c(10850)ArcLOADP_LoadArchive:Current state msg_id=1110
17728:140080102217504 08/14/2016 02:10:56:160606 ERROR arsload.c(15986)ArcLOAD_ProcessFile:Current state msg_id=1117
17728:140080102217504 08/14/2016 02:10:56:176486 ERROR (null)(0)(null):Sending message to library server msg timestamp=2016-08-14 02:10:56.160742 msg userid=ADMIN msg severity=2 msg num=88 msg text=ARS0088E Application Group Failed Load: Name(ITEST) LoadId(5016-1-0-4FAA-20161031000000-20161031000000-5017) File(/tmp/input/sample) msg appl=T msg logid=1538490249
17728:140080102217504 08/14/2016 02:10:56:176513 ERROR (null)(0)(null):CONSOLE message msg num=88
17728:140080102217504 08/14/2016 02:10:56:176532 ERROR (null)(0)(null):ARSLOG message msg num=88
17728:140080102217504 08/14/2016 02:10:56:179396 ERROR arsloadc.c(4476)ArcLOADC_Main:Current state msg_id=1126
http://www-01.ibm.com/support/docview.wss?uid=swg27019582 (http://www-01.ibm.com/support/docview.wss?uid=swg27019582)
this is the technotes on how to do it.
Now... in the application group, you have a button called "Advanced" in the general tab, you can define there how CMOD will handle each segment tables, in its own tablespace, or in a SMS, automatic storage, or none...
For oracle, you should look what you want to do, and since you are going the road of remote database, then you must also read in the link above the following text:
QuoteWhen choosing the following option for the application group database storage: System Managed Space Table Space - SMS (DB2), Use Tablespace (Oracle), or Use File groups (Microsoft SQL Server), Content Manager OnDemand looks for the directory, based on the ars.dbfs, that has the most available space to create the tablespace or file group. However, when the database server is remote, it is impossible for Content Manager OnDemand to analyze the available file systems on the remote server. The Content Manager OnDemand tablespace creation user exit must be created and used. See the arscsxit.h (in the installation directory) for information on the tablespace creation user exit.
Meaning, that depending on the option you have chosen, then you might need to write a tablespace user exit. If you don't care about tablespaces, then put the option to none, and you don't need to write/compile anything.
If you want to use the option tablespace, then you MUST create a tablespace user exit.
Alessandro, thanks for your reply. Yes I have resolved the issue last night forgot to update here. I read the link you provided earlier but could not figure out what exactly that mean and could not right away think of connecting to the use tablespce option on the advanced tab.
The resolution is,
- DBA to create tablespace in remote DB and assigned that to the userid.
- CMOD Admin to unselect use tablespace option in appgroup - advanced screen
Now need to figure out if thee is any performance issue in the long run.
Performance? I am don't think so...
But the backups... definitely yes and especially for the restore... that will be a nightmare for the DBA...
My advice would be, if you can, and have the capability (you or someone in your company), to discuss with the DBA what is the best way to handle tablespaces, and define a tablespace strategy for the cmod database.
And the next step would be to use the tablespace user exit to create the tablespace according to the define strategy in order to simplify the backup/restore in the future.
As long as your DB is small... there are no problems, but at one point, your DBA will feel the pain.
Did talk to my DBA, they do not have a clue about tablespace strategy, either theyr are busy or really do not know.
Can you suggest a sample strategy that would be helpful?
Quote from: SV on August 27, 2016, 12:13:53 AM
Did talk to my DBA, they do not have a clue about tablespace strategy, either theyr are busy or really do not know.
Can you suggest a sample strategy that would be helpful?
Well if he has no idea... then don't use tablespace, (change the option in CMOD AG) to not use tablespaces. And maybe he has some strategy with Oracle to not be worried and live a peaceful life.
I am not a DBA and even less an Oracle DBA, so I might not know everything on that field.
All I know was that the Oracle DBA I spoke with, they were concerned. More than that, I cannot say!