Author Topic: image indexing  (Read 8838 times)

vaios

  • Guest
image indexing
« on: January 25, 2011, 02:03:48 AM »
Hi,

I am trying to arsload imagges(tiff) on my CMOD Server (8.4.1). I created my application group like that
Database Field names (ldate,name,company,subject).......field Information (ldate (data type string 20), name (data type string 60), company (data type string 60), subject (data type string 60)).
I created my application like that:
Data type: tiff
Indexer: Generic
Load Information : Data compression --disable

I created an image001.ind as an index file which is like that:
CODEPAGE:819
GROUP_FIELD_NAME: ldate
GROUP_FIELD_VALUE:01/01/2011
GROUP_FILENAME:Image001.tif


I now copy in my /bin folder both image001 and image001.ind files and run the following command
C:\IBM\OnDemand for WinNT\bin>arsload -u admin -p "XXXX" -n -g APPLGR Ima
ge001.tif -a APPL
arsload: Processing file >Image001.tif<

arsload: 01/25/11 11:01:31 -- Indexing started, 645084 bytes to process
arsload: Generic Indexer requires the data to have already been indexed.  Index
the data or verify your input file and resubmit the job
arsload: Output/Indexer file was not created
arsload: 01/25/11 11:01:31 Indexing failed
arsload: Processing failed for file >Image001.tif<
arsload: Unloading of data was NOT performed
arsload: Processing has stopped.  The remaining files will NOT be processed.

CAN you help me?????

pankaj.puranik

  • Sr. Member
  • ****
  • Posts: 374
    • View Profile
Re: image indexing
« Reply #1 on: January 25, 2011, 02:17:10 AM »
When you are using the generic indexer, you don't have to mention the tiff file name in the arsload command.
Instead you should be using the name of the .ind file without the .ind extension.
In your case it should look like this :

C:\IBM\OnDemand for WinNT\bin>arsload -u admin -p "XXXX" -n -g APPLGR -a APPL image001

This means we have to supply the .ind file name and not the actual file name.
Why this is so? It is because the .ind file allows you to have multiple enteries for multiple files. Eg.

CODEPAGE:819
GROUP_FIELD_NAME: ldate
GROUP_FIELD_VALUE:01/01/2011
GROUP_OFFSET:0
GROUP_LENGTH:0
GROUP_FILENAME:C:\XYZ\Image001.tif

GROUP_FIELD_NAME: ldate
GROUP_FIELD_VALUE:01/01/2011
GROUP_OFFSET:0
GROUP_LENGTH:0
GROUP_FILENAME:C:\XYZ\Image002.tif

So the indexer picks the actual file name and absolute path of the file from the GROUP_FILENAME entry.

Hope this helps resolve your problem.


vaios

  • Guest
Re: image indexing
« Reply #2 on: January 25, 2011, 02:56:11 AM »
Thnx for your help . I now have this

CC:\IBM\OnDemand for WinNT\bin>arsload -u admin -p "XXXXX" -n -g APPLGR -a
APPL image001
arsload: Processing file >image001<

arsload: 01/25/11 11:54:18 -- Loading started, --UNKNOWN-- bytes to process
OnDemand Load Id = >5021-1-0-3FAA-0-0<
An error occurred.  Contact your System Administrator and/or consult the System
Log.  File=arsadmp.c, Line=1553
Failed while attempting to load the database
Loaded 0 rows into the database
arsload: 01/25/11 11:54:19 Loading failed
arsload: Processing failed for file >image001<
arsload: Unloading of data was NOT performed
arsload: Processing has stopped.  The remaining files will NOT be processed.



By the way Do u know where i can find the valid code page matrix for CODEPAGE parameter?





pankaj.puranik

  • Sr. Member
  • ****
  • Posts: 374
    • View Profile
Re: image indexing
« Reply #3 on: January 25, 2011, 03:06:31 AM »
Well, for code page, 819 is for TIFF. I don't have pointers to the CODEPAGE for other types right now.

Here's something that's mentioned in the IBM documentation. Are you using absolute path in the ind file?

Troubleshooting scenario 6:
 ARSLOAD cannot find the TIFF images when using generic index Symptom
While running ARSLOAD to automatically load data into OnDemand, each load fails.

Possible causes
 It is possible that you did not specify full file names. The generic index file format requires that you specify absolute file names, that is, full file names.

Action
Make sure that you specify absolute file names. If you cannot make this happen, try to run separate ARSLOAD command daemons for each download directory, and start them up by making sure that they are invoked from the download directory in which they monitor.

pankaj.puranik

  • Sr. Member
  • ****
  • Posts: 374
    • View Profile
Re: image indexing
« Reply #4 on: January 25, 2011, 03:11:23 AM »
One more thing. I see that you have four fields (ldate,name,company,subject). However in the ind file you have only mentioned ldate (the error that you are getting is not repated to this.).
Please have the enteries for other fields also for now.
Make sure that the library server and object server are running.

By the way, what OS are you using?

pankaj.puranik

  • Sr. Member
  • ****
  • Posts: 374
    • View Profile
Re: image indexing
« Reply #5 on: January 25, 2011, 03:17:48 AM »
I just realized that I had the same issue.
Check out the following threads.

http://www.odusergroup.org/forums/index.php?topic=453.0
http://www.odusergroup.org/forums/index.php?topic=443.0

vaios

  • Guest
Re: image indexing
« Reply #6 on: January 25, 2011, 04:34:04 AM »
My OS is win 2003 sp2

I feel the i did not follow the installation manual ( i don' t have odadmin user in my os)
i will reinstall and I will let you know.

Thanx

pankaj.puranik

  • Sr. Member
  • ****
  • Posts: 374
    • View Profile
Re: image indexing
« Reply #7 on: January 25, 2011, 04:42:46 AM »
Yes you should follow the instructions in the admin guide.
It clearly mentions the rights the user should have and the local security policies.

So the first step would be to create the user as mentioned in the redbook.
Then install DB2 and use the same user that you created in the previous step.
Then you can go ahead with installing the CMOD server, etc.

vaios

  • Guest
Re: image indexing
« Reply #8 on: January 25, 2011, 04:52:09 AM »
We run a parallel load on z/os. and we get the following error.
Do you have any experience on that platform?
CMOD 7.1.2.9
z/os 1.10

Imag001.IND file:
CODEPAGE:819                                 
GROUP_FIELD_NAME:company                     
GROUP_FIELD_VALUE:product                     
GROUP_OFFSET:0                               
GROUP_LENGTH:0                               
GROUP_FILENAME:/usr/lpp/ars711/bin/imag001.tif

the command:
arsload -h ARCHIVE -u admin -p XXXXXXXX -g AGRP -a APRP /usr/lpp/ars711/bin/imag001

the output:
arsload: Using /ars/tmp for temporary files                                 
arsload: Processing file >/usr/lpp/ars711/bin/imag001<                     
arsload: Unable to log load information                                     
arsload: Processing has stopped.  The remaining files will NOT be processed.



pankaj.puranik

  • Sr. Member
  • ****
  • Posts: 374
    • View Profile
Re: image indexing
« Reply #9 on: January 27, 2011, 11:30:33 PM »
This is happenning probably because you don't have the System Log folder.
You need to run the arssyscr command.  Check the Installation Guide for more information.

As recommended by JD in one of the other threads, run this while CMOD is down -- but DB2 needs to be up.

http://www.odusergroup.org/forums/index.php?topic=445.0

Let us know if your problem gets solved.

I don't have any experience in Z o/s.
I have worked on AIX and Windows.



Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2229
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: image indexing
« Reply #10 on: January 29, 2011, 07:33:14 AM »
Unless I missed something, the load error doesn't seem to point to a missing System Log.  He may need to check the db2diag.log file, or the event viewer for more information on the error that is preventing loading.  Let us know what you find, Vaios.

-JD.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR