Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Gobi21

Pages: 1 [2] 3
16
Other / Re: Ondemand Crashed
« on: November 12, 2013, 05:35:43 AM »
Hi Alessandro,

I have managed to get the last day working DB Log and here is the error message i can find:

TNS-12518: TNS:listener could not hand off client connection
 TNS-12547: TNS:lost contact
  TNS-12560: TNS:protocol adapter error
   TNS-00517: Lost contact
    Solaris Error: 32: Broken pipe


17
Other / Re: SnapLock Upgrade
« on: November 12, 2013, 04:20:10 AM »
Hi Alessandro,

Thanks for the update. Will check with TSM

18
Other / Re: Ondemand Crashed
« on: November 12, 2013, 04:04:48 AM »
Hi Alessandro,

Thanks for the reply. Thats a good view.

I am using CMOD 8.4.1 with Oracle 10.2.0.4.0 - 64bit. we have smiliar setup in other servers and its working fine.

I tried using SQLPLUS Command and i am able to execure a sample query. Its looking good.

Even tnsping <Instance name> from the server is working fine.

There is no change in the tnsnames.ora for the past three years.

I have no clue since the Ondemand crashed just like that when i was perfoming deletion of an Application Group.

Thanks for your help again.

19
Other / Re: Ondemand Crashed
« on: November 12, 2013, 12:36:42 AM »
Hi Siva,

Thanks for the reply. I have reverted back the old password in CFG file after Checking with the new password.

So the current CFG File has old password only. I am not able to bring the service up still.

Thanks,
Gobi

20
Other / SnapLock Upgrade
« on: November 11, 2013, 07:30:15 AM »
Hi All,

Please let me know if we upgrade the Snaplock from 7.3.6 version to 8.1.3 Netapp, do we need to change anything from CMOD/TSM config files?.
We have many filers and we are planning to upgrade the same to 8.1.3.

Thanks

21
Other / Ondemand Crashed
« on: November 11, 2013, 07:25:10 AM »
Hi All,

I was working with CMOD Admin and deleted a Application Group. While deleting the group, it asked for a confirmation and suddenly the Ondemand got disconnected.
I started Ondemand after that and it is not running now.Here is the error message:

25225    1        0000000000000001 11/11/13 09:56:54.173995 INFO   ArcDB_Init Connecting to database (type=2, name=xxxxxxxx)
25225    1        0000000000000001 11/11/13 09:56:58.368366 ERROR  ArcDB_Init Unable to establish connection to the database
25225    1        0000000000000001 11/11/13 09:56:58.369039 ENTER  ArcDBP_ErrorCheck
25225    1        0000000000000001 11/11/13 09:56:58.369997 ENTER  ArcDB_Commit
25225    1        0000000000000001 11/11/13 09:56:58.370416 ENTER  ArcDBP_Commit
25225    1        0000000000000001 11/11/13 09:56:58.373284 RETURN ArcDBP_Commit RC=-1
25225    1        0000000000000001 11/11/13 09:56:58.373853 RETURN ArcDB_Commit RC=6
25225    1        0000000000000001 11/11/13 09:56:58.386605 ERROR  ArcDBP_ErrorCheck A DB error message issued. Check System Log or System Console
25225    1        0000000000000001 11/11/13 09:56:58.387311 RETURN ArcDBP_ErrorCheck RC=6
25225    1        0000000000000001 11/11/13 09:56:58.387864 RETURN ArcDB_Init RC=6
25225    1        0000000000000001 11/11/13 09:56:58.388328 ENTER  ArcDB_Cancel
25225    1        0000000000000001 11/11/13 09:56:58.388768 RETURN ArcDB_Cancel
25225    1        0000000000000001 11/11/13 09:56:58.389243 ENTER  ArcDB_Shutdown
25225    1        0000000000000001 11/11/13 09:56:58.389643 INFO   ArcDB_Shutdown Free the OnDemand application handles
25225    1        0000000000000001 11/11/13 09:56:58.390076 ENTER  ArcDBP_FSTerm
25225    1        0000000000000001 11/11/13 09:56:58.390633 RETURN ArcDBP_FSTerm
25225    1        0000000000000001 11/11/13 09:56:58.391557 ENTER  ArcDBP_TermOptions
25225    1        0000000000000001 11/11/13 09:56:58.392001 RETURN ArcDBP_TermOptions
25225    1        0000000000000001 11/11/13 09:56:58.392332 ENTER  ArcDBP_TermTableNames
25225    1        0000000000000001 11/11/13 09:56:58.392760 RETURN ArcDBP_TermTableNames
25225    1        0000000000000001 11/11/13 09:56:58.393340 ENTER  ArcDBP_UnLoadDBMS
25225    1        0000000000000001 11/11/13 09:56:58.393765 INFO   ArcDBP_UnLoadDBMS Unloading database module
25225    1        0000000000000001 11/11/13 09:56:58.394162 RETURN ArcDBP_UnLoadDBMS
25225    1        0000000000000001 11/11/13 09:56:58.394566 RETURN ArcDB_Shutdown RC=0
25225    1        0000000000000001 11/11/13 09:56:58.395075 INFO   ArcSERVP_ArchiveServer Number of db servers to use: 20
25225    1        0000000000000001 11/11/13 09:56:58.395525 RETURN ArcSERVP_ArchiveServer RC=6
25225    1        0000000000000001 11/11/13 09:56:58.395941 ENTER  ArcCSL_LockTerm
25225    1        0000000000000001 11/11/13 09:56:58.396417 RETURN ArcCSL_LockTerm RC=0
25225    1        0000000000000001 11/11/13 09:56:58.399468 INFO   ArcTRACE_Term Trace function terminated


I have checked with database team and they told that DB is UP and Running. I am not able to get the exact error message from the above trace log. I have changed the database password in ars.cfg file, however while connecting via TOAD, i am able to access only with the old password.Hence, Ondemand didnt come to a point where it has to read the ars.cfg file.

Could you please help me on this?.

22
Other / Re: Decimal Precision issue
« on: August 02, 2013, 01:02:15 AM »
Hi all,

I got to know it is an known issue in CMOD 8.4.1 version and there is a Fix note available.

http://www-01.ibm.com/support/docview.wss?uid=swg1PM37226


Cheers,
Gobi

23
Other / Decimal Precision issue
« on: August 01, 2013, 05:59:06 AM »
Hi ,

I am using the commands to create Folder structure in the CMOD.  Below are the commands..

<field name="GIT" description="GIN" fieldType="Decimal" mappingType="Single">
<mapping dbName="GIT" appGroup="TESTF003_1"/>
<fieldInfo group="*PUBLIC" displayOrder="5" queryOrder="5" sortOrder="5" equal="Default" notEqual="Yes" lessThan="Yes" ltOrEqual="Yes" greaterThan="Yes" gtOrEqual="Yes" in="Yes" notIn="Yes" between="Yes" notBetween="Yes" decimalPrecision
="0"/>
</field>


<field name="AMOUNT1" description="AMOUNT" fieldType="Decimal" mappingType="Single">
<mapping dbName="AMOUNT1" appGroup="TESTF003_1"/>
<fieldInfo group="*PUBLIC" displayOrder="7" queryOrder="7" sortOrder="7" equal="Default" notEqual="Yes" lessThan="Yes" ltOrEqual="Yes" greaterThan="Yes" gtOrEqual="Yes" in="Yes" notIn="Yes" between="Yes" notBetween="Yes" decimalPrecision
="6"/>
</field>


Whereever i have the configuration as decimalPrecision= "0", the decimalprecision is updated as "2" instead of "0". The second query updated the decimalprecision as "6" as designed.

It looks very strange for me.

please help me with your insights on this issue.

24
Other / Re: New Line Character
« on: August 01, 2013, 05:49:30 AM »
Sure Justin. I have requested the source team to correct the file delivered from them. I have also informed the CMOD requirements and hopefully they will accept the changes in their side.

Hi Alessandro,

That helps a lot  :).. Thanks for your time and effort. very much appreciate..


Cheers,
Gobi

25
Other / Re: New Line Character
« on: July 30, 2013, 12:14:02 AM »
Hi All,

Thanks for your valuable suggestions and comments.


Cheers,
Gobi

26
Other / Re: New Line Character
« on: July 29, 2013, 07:09:59 AM »
Hi Justin,

We have this information notified in CMOD Documentation?. Customer is requesting reference from CMOD as evidence.

please help me if you have this detail.

Thanks,
Gobi


27
Other / Re: New Line Character
« on: July 29, 2013, 04:41:48 AM »
I will work to correct the Index file after the creation.

Thanks a lot Alessandro and Justin for your inputs.

Cheers,
Gobi

28
Other / Re: New Line Character
« on: July 29, 2013, 02:14:51 AM »
Hi Alessandro,

Thanks for your reply. Here are the details.

I am not passing the .IND in the arsload command.

You can have a look in the IND file details and you can see the parsed line where we have issue in the processing.
IND File Format:
------------------
CODEPAGE:1208
COMMENT:------- Document 1 -------
GROUP_FIELD_NAME:COUNTERPRTY_NAME
GROUP_FIELD_VALUE:legal_name0000001
.
.
.
GROUP_OFFSET:10
GROUP_LENGTH:3870
GROUP_FILENAME:EGZATEST.TEST.DN.20130609.S001.V002.U002.Data.txt


Record in Issue:
-------------------
COMMENT:------- Document 7 -------
GROUP_FIELD_NAME:COUNTERPRTY_NAME
GROUP_FIELD_VALUE:Testi_
name6248320
GROUP_FIELD_NAME:ENTITY_ID
GROUP_FIELD_VALUE:
.
.
.

In the CMOD Admin, i am seeing the indexing as "Generic" for this Application.

we have the input file received from application team with the lines parsed as above and hence the IND file is also created in the same format. I want to know whether arsload will be able to process the IND file even if have parsed lines as above.(You may see that the GROUP_FIELD_VALUE value is available in two lines instead of one!!).. is it causing the issue in the CMOD processing?.

The documents till the parsed one are getting ingested sucessfully and the arsload throwed the "Invalid generic index file format: >name6248320<" while processing the parsed document. I am able to see the Load ID created in the log file for this processing.


Thanks again for your support.

Regards,
Gobi


29
Other / Re: New Line Character
« on: July 25, 2013, 12:39:52 AM »
Hi Pankaj,

It is using generic index only.
Thanks for the response. Please find the below parsed IND file record snap which is used by arsload. CMOD is getting stucked up while reading this record.

Key><KeyName>COUNTERPRTY_NAME</KeyName>
<KeyValue><![CDATA[legal_
name0000001]]></KeyValue></Key>
<Key><KeyName>ENTITY_ID</KeyName>
<KeyValue></KeyValue></Key>


Let me know if you need any other detail.

30
Other / New Line Character
« on: July 19, 2013, 06:55:50 AM »
Hi All,

I have a field definition for one of the variable as "string" in one of the application group.  In the input file, source team has added a newline character in that field. We ingested the files in CMOD and received error message "Invalid Generic format".

Is it due to the newline character added in the field?.. Normally CMOD will accept the newline character?.

Your help is very much appreciated. Thanks.

Pages: 1 [2] 3