Fatal error in server row processing - SQL error -
Posted in 2009
Topics: Storage & Space Management, Error Codes & Troubleshooting, Migration, Import/Export & Data Conversion, Platform-Specific Issues
IDS 11.50.FC5 AIX 5.3 (4k Page Size)
We did a HPL unload from a table using the schema below:
create table "ifxrept".rptrepositoryfile
(
i_reportfile_id serial not null ,
i_repository_id integer,
i_filetype_id integer,
b_file_byte byte in reportsblob,
c_process_user char(8),
d_process_date date,
c_process_time char(8),
primary key (i_reportfile_id)
) extent size 148738 next size 25496 lock mode row;
We then tried loading it into a new table using the following schema:
create table "ifxrept".rptrepositoryfile_a
(
i_reportfile_id serial not null ,
i_repository_id integer,
i_filetype_id integer,
b_file_byte blob,
c_process_user char(8),
d_process_date date,
c_process_time char(8)
)
extent size 148738 next size 25496 lock mode row;
ALTER TABLE rptrepositoryfile_aPUT b_file_byte IN (reportsbs);
(Unrelated but couldn't figure out how to blend the PUT statement into the
CREATE TABLE without a syntax error)
HPL Load processed 12 rows then died with the following error:
Fatal error in server row processing - SQL error -63 ISAM error 0
-63 File name too long.
An operating-system error code with the meaning shown was unexpectedly
returned to the database server. An error might exist in the coding of a
REPORT TO statement of a report. If not, note all circumstances and contact
IBM Technical Support.
Any ideas why? Thanks in advance.
Clifton
_________________________________________________________________
Windows 7: I wanted simpler, now it's simpler. I'm a rock star.
http://www.microsoft.com/Windows/windows-7/default.aspx?h=myidea?ocid=PID24727::
T:WLMTAGL:ON:WL:en-US:WWL_WIN_myidea:112009
Dunno if ya did this already - but look in the log file that hpl creates,
usually /tmp to see if there is anymore detail. You may also dicker with
onpladm commands to list and describe the various elements of the HPL load job
- you may find the error come up again. You could try onstat -j if the job
doesn't kill hpl entirely:
http://publib.boulder.ibm.com/infocenter/idshelp/v10/topic/com.ibm.hpl.doc/hplms
t362.htm#sii-xfonstat-15414
Good luck -
MM