Sql loader error in offline data load
Hi,
I have done an offline schema creation using existing tablespace.
I am trying to do an offline data load using sql loader.The CTL and DAT file are generated by the work bench.
This is my CTL file code generated by workbench.
load data
infile 'Import.dat' "str '<EORD>'"
into table IMPORT
fields terminated by '<EOFD>'
trailing nullcols
When I am running the ctl file with DAT file in sql loader I am getting the following error
SQL*Loader-350: Syntax error at line 4.
Expecting single char, found "<EOFD>".
fields terminated by '<EOFD>'
^
My Sql Loader version is Release 8.0.6.3.0
Please help if anyone has came across this issue.
Thanks in advance.
Regards
Saravanan.B
Saravanan,
Its a long time since I have seen 8 sql loader. Check the doc. Is it resrticted to a single character delimter??
Barry
Similar Messages
-
How to rectify the errors in master data loads & transactional data loads?
hy,
please any one tell me
How to rectify the errors in master data loads & transactional data loads?
thnQ
RaviHi,
Please post specific questions in the forum.
Please explain the error you are getting.
-Vikram -
Error in Master data load because of ###
Hello,
I am getting an error in master data load.
The problem is ####### symbols are encountered in few records.
We have defined a formula to replace the ### with S in transfer structure.
But still it does not replace the #### symbols and gives error.
But when I insert the ####### symbols manually in PSA and try to load it is replaced with the formula definition and loads the data.
Suggestions required urgently
Thanks in advance
RamHello srikanth,
Check the code below.
I have used it in the update rule to replace the #### symbol with A.
But when i check in debug mode it is not recognizing this symbol and sy-subrc ia always 4.
GV_STRING = COMM_STRUCTURE-/BIC/XXX
FIND '#' in R_STRING.
IF SY-SUBRC = 0.
REPLACE ALL OCCURRENCES OF '#' in R_STRING with 'A'.
ENDIF.
result value of the routine
RESULT = R_STRING
Thanks
Ram -
I have been developing a VI file that has
been working fine, until now. I am using 8.6.
Every time I attempt to open this file
I keep getting:
How do I fix the error code:
Labview: Memory is
full.
An error occurred loading VI. LabView load error code 1:
LabView load error code %ld: %p”
On a separate dialog:
“Not enough memory to complete this
operation.”
I ran VI analyzer which told that the
VI:
One or more errors occurred during
analysis.
Testing errors tab – Vi not loadable
and my file name. At the bottom in the error description I got:
“Error 74. Memory or data structure
corrupt. <my file path> and <file name>.”
Could not be opened.
Is there anything I can do to recover
the file?Hi kevin_khan,
I went ahead and tried to open it and got the error attached.
Peter T
Applications Engineer
National Instruments
Attachments:
test.png 14 KB -
LabVIEW load error code 1: LabVIEW load error code %Id: %p
One of my VI crashed while trying to save some data to file, I then tried to save the VI afterwards, but message with Out of Memory popped up again and the IV closed down. So now I can´t open my VI, then I try I get the "LabVIEW load error code 1: LabVIEW load error code %Id: %p" message and I have been given no opportunity to recover an older version of the VI then I close down and open LabVIEW again!!! So my VI is lost or what?
This is a huge problem for me, hope someone can help...
Regards
JesperHi Jesper
For the future you should be good with LabVIEW 2012 (Normally realeased after NI Week in Austin in beginning of August). From what I know about this problem it have not been mentioned to be solved in a fixpack before release of LabVIEW 2012.
If you are reading in large files that uses more memory than avaliable and do wan't to avoid LabVIEW from crashing then you could add more RAM to your PC. If you are using Windows 32-bit you could try to edit the boot.ini file for Windows to allow Windows to allocate more memory to LabVIEW as explained in the following article:
Extending Virtual Memory Usage for 32-bit Windows
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/enable_lrg_ad_aware/
You could also try upgrading to Windows 64-bit this will allow much larger memory operations, and Windows 64-bit will let LabVIEW allocate more memory.
To use Source Code Control on your computer you will need:
1) A Source Code Control server with space to store the backup VI's and previous versions on (this can be your own PC). All Source Code Control providers that follow the Microsoft Source Code Control API. We have a list of tools that we have been tested that can be found here (note that some is free and other is not):
Which Third-Party Source Control Providers Can I Use with LabVIEW 8.0 and later?
http://digital.ni.com/public.nsf/websearch/26EC5904169430CE8625706E00743997?OpenDocument
2) After installing the server you need to configure LabVIEW to communicate with this server. In the article below under the section "Configuring LabVIEW to Call the Microsoft SCC API" you can see how to do this:
Software Configuration Management and LabVIEW
http://zone.ni.com/devzone/cda/tut/p/id/4114
3) You are good to go. Source Code Control uses the two most know functions "Commit / Check out." When you Check out a document you will be able to edit it, and when you then commit the changes then it will be saved with a new version number on the server. For each commit you will be able to select "Revert to previous version" to go back and restore a previous commited VI. You can use these functions on the VI it self or as I prefer from the Project Explorer.
Bisides the advantage of being able to restore previous versions, Source Code Control is also a great tool if your are multiple users working on the same project. You will i.e. be able to be 2 or more developers working on the same VI at the same time and then merging your changes to one VI when you are finished.
Best Regards
Anders Rohde
Applications Engineer
National Instruments Denmark -
SQL Loader Error : ORA-01830: date format picture ends before converting en
I am inserting following data
BES101706 M.E. Deals 7 10/17/2006
through control file :
LOAD DATA
APPEND
INTO TABLE abc_temp
FIELDS TERMINATED BY ' '
TRAILING NULLCOLS
(BATCH_NAME ,
SUPPLIER_NAME ,
SUPPLIER_NBR ,
INV_DATE "to_date(substr(:INV_DATE,1,10),'MM/DD/YYYY' )"
But I am getting this error:
ORA-01830: date format picture ends before converting entire input string
inv_data is a date field in the database.I think it has to do with data format.Exactly.
You have
BES101706*M.E.*Deals*7*10/17/2006
I replace each space with an asterisk. You have 5 columns according to your spec (terminated by '<space>')
SQL Loader doesn't know that M.E. Deals is the supplier name.
It's trying to convert 7 as the date. -
SQL*Loader Error Field in data file exceeds maximum length", version 8.1.6
Hi All,
I am trying to load a data file into a database table using SQL loader. I
received the data in an data file but I saved it as a pipe delimited
file.
When I run the SQL Loader command no records are loaded - looking at the log
file I get the following error:
Rejected - Error on table FARESDATA, column FANOTESIN.
Then I tried with substr and doesnt seem to work for values greater than 4000 chars, it only works if the field value is below 4000 chars (say doing a substr for first 3000 chars).
see the code--------
LOAD DATA
INFILE 'p.dat'
APPEND INTO TABLE PROSPECTUS
FIELDS TERMINATED BY '|' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
Fanotesin char(4000) "substr(:fanotesin,1,4000)"
We get the error ORA-01461: can bind a LONG value only for insert into a LONG column when using substr for 4000 chars.
Please help!
Thanks,
Rajesh
nullI believe the problem here is that the ORACLE database regards anything > 4000chs as a CLOB (or LONG). 4000 is the maximum length of a varchar2 field in the database, although of course you can declare larger values in PL/SQL. (Since the incoming data is > 4000 chs it is regarded as a LONG and you cannot therefore use SUBSTR on it)
I think that you must either truncate your data before loading or load into a table with the offending field as a CLOB (or LONG)
and then use PL/SQL to recreate it in a table with a varchar2(4000) which is otherwise identical. (You can select from a LONG into a varchar2(32000) for example and then truncate before writing out to the new table). -
Error Message after data load (error is "1130610")
We load data using a data load rule. The data seems to load fine except we get the error message "ERROR - 1241101 - Unexpected Essbase error 1130610" on last line below? Any thoughts? Is there a guide somewhere that explains in details all the various error codes and what they refer to? We're using Essbase 6.5.1. Thanks!======================================= OK/INFO - 1003037 - Data Load Updated [364875] cells. OK/INFO - 1003024 - Data Load Elapsed Time : [428.323] seconds. ERROR - 1241101 - Unexpected Essbase error 1130610.=======================================
The explanation of error 1130610 is the following:Possible Problems - Essbase cannot open a file. Possible Solutions - If you are using an error file, make sure that the error file is being created in a directory that already exists. Make sure you are using the ESSCMD IMPORT command correctly. Put all files the ESSCMD script needs in the $ARBORPATH\APP\applicationName\databaseName directory. Run the ESSCMD script from the $ARBORPATH\APP\applicationName\databaseName directory. Check the ESSCMD script for invalid paths. Make sure every folder that the script is pointing to exists. If you are using an error file, make sure that the error file is being created in a directory that already exists.
-
Error while starting data loading on InfoPackage
Hi everybody,
I'm new at SAP BW and I'm working in the "Step-By-Step: From Data Model to the BI Application in the web" document from SAP.
I'm having a problem at the (Chapter 9 in the item c - Starting Data Load Immediately).
If anyone can help me:
Thanks,
Thiago
Below are the copy of the error from my SAP GUI.
<><><><><><><><><><<><><><><><><><><><><><><><><><><><><><><><>
Runtime Errors MESSAGE_TYPE_X
Date and Time 19.01.2009 14:41:22
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
Batch - Manager for BW Processes ***********
Long text of error message:
Technical information about the message:
Message class....... "RSBATCH"
Number.............. 000
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSBATCH" or "LRSBATCHU01"
"RSBATCH_START_PROCESS"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 701
Application server... "sun"
Network address...... "174.16.5.194"
Operating system..... "Windows NT"
Release.............. "5.1"
Hardware type........ "2x Intel 801586"
Character length.... 8 Bits
Pointer length....... 32 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "localhost"
Database type..... "ADABAS D"
Database name..... "NSP"
Database user ID.. "SAPNSP"
Terminal.......... "sun"
Char.set.... "English_United State"
SAP kernel....... 701
created (date)... "Jul 16 2008 23:09:09"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQLDBC 7.6.4.014 CL 188347 "
Patch level. 7
Patch text.. " "
Database............. "MaxDB 7.6, MaxDB 7.7"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 8112
EM...... 11498256
Heap.... 0
Page.... 65536
MM Used. 6229800
MM Free. 1085264
User and Transaction
Client.............. 001
User................ "THIAGO"
Language key........ "E"
Transaction......... "RSA1 "
Transactions ID..... "CD47E6DDD55EF199B4E6001B782D539C"
Program............. "SAPLRSBATCH"
Screen.............. "SAPLRSS1 2500"
Screen line......... 7
Information on where terminated
Termination occurred in the ABAP program "SAPLRSBATCH" - in
"RSBATCH_START_PROCESS".
The main program was "RSAWBN_START ".
In the source code you have the termination point in line 340
of the (Include) program "LRSBATCHU01".
Source Code Extract
Line
SourceCde
310
endif.
311
l_lnr_callstack = l_lnr_callstack - 1.
312
endloop. " at l_t_callstack
313
endif.
314
315
*---- Eintrag für RSBATCHHEADER -
316
l_s_rsbatchheader-batch_id = i_batch_id.
317
call function 'GET_JOB_RUNTIME_INFO'
318
importing
319
jobcount = l_s_rsbatchheader-jobcount
320
jobname = l_s_rsbatchheader-jobname
321
exceptions
322
no_runtime_info = 1
323
others = 2.
324
call function 'TH_SERVER_LIST'
325
tables
326
list = l_t_server
327
exceptions
328
no_server_list = 1
329
others = 2.
330
data: l_myname type msname2.
331
call 'C_SAPGPARAM' id 'NAME' field 'rdisp/myname'
332
id 'VALUE' field l_myname.
333
read table l_t_server with key
334
name = l_myname.
335
if sy-subrc = 0.
336
l_s_rsbatchheader-host = l_t_server-host.
337
l_s_rsbatchheader-server = l_myname.
338
refresh l_t_server.
339
else.
>>>>>
message x000.
341
endif.
342
data: l_wp_index type i.
343
call function 'TH_GET_OWN_WP_NO'
344
importing
345
subrc = l_subrc
346
wp_index = l_wp_index
347
wp_pid = l_s_rsbatchheader-wp_pid.
348
if l_subrc <> 0.
349
message x000.
350
endif.
351
l_s_rsbatchheader-wp_no = l_wp_index.
352
l_s_rsbatchheader-ts_start = l_tstamps.
353
l_s_rsbatchheader-uname = sy-uname.
354
l_s_rsbatchheader-module_name = l_module_name.
355
l_s_rsbatchheader-module_type = l_module_type.
356
l_s_rsbatchheader-pc_variant = i_pc_variant.
357
l_s_rsbatchheader-pc_instance = i_pc_instance.
358
l_s_rsbatchheader-pc_logid = i_pc_logid.
359
l_s_rsbatchheader-pc_callback = i_pc_callback_at_end.Hi,
i am also getting related this issue kindly see this below short dump description.
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
Variant RSPROCESS0000000000705 does not exist
Long text of error message:
Diagnosis
You selected variant 00000000705 for program RSPROCESS.
This variant does not exist.
System Response
Procedure
Correct the entry.
Technical information about the message:
Message class....... "DB"
Number.............. 612
Variable 1.......... "&0000000000705"
Variable 2.......... "RSPROCESS"
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSPC_BACKEND" or "LRSPC_BACKENDU05"
"RSPC_PROCESS_FINISH"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 701
Application server... "CMCBIPRD"
Network address...... "192.168.50.12"
Operating system..... "Windows NT"
Release.............. "6.1"
Hardware type........ "16x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "CMCBIPRD"
Database type..... "MSSQL"
Database name..... "BIP"
Database user ID.. "bip"
Terminal.......... "CMCBIPRD"
Char.set.... "C"
SAP kernel....... 701
created (date)... "Sep 9 2012 23:43:54"
create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 196
Patch text.. " "
Database............. "MSSQL 9.00.2047 or higher"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0, Windows NT 6.1, Windows NT 6.2"
Memory consumption
Roll.... 16192
EM...... 4189840
Heap.... 0
Page.... 16384
MM Used. 2143680
MM Free. 2043536
User and Transaction
Client.............. 001
User................ "BWREMOTE"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "9C109BE2C9FBF18BBD4BE61F13CE9693"
Program............. "SAPLRSPC_BACKEND"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "BIP"
Database Release.... 701
Kernel Release...... 701
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "asynchron without reply and transactional (emode 0, imode
0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Information on where terminated
Termination occurred in the ABAP program "SAPLRSPC_BACKEND" - in
"RSPC_PROCESS_FINISH".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 75
of the (Include) program "LRSPC_BACKENDU05".
Source Code Extract
Line SourceCde
45 l_t_info TYPE rs_t_rscedst,
46 l_s_info TYPE rscedst,
47 l_s_mon TYPE rsmonpc,
48 l_synchronous TYPE rs_bool,
49 l_sync_debug TYPE rs_bool,
50 l_eventp TYPE btcevtparm,
51 l_eventno TYPE rspc_eventno,
52 l_t_recipients TYPE rsra_t_recipient,
52 l_t_recipients TYPE rsra_t_recipient,
53 l_s_recipients TYPE rsra_s_recipient,
54 l_sms TYPE rs_bool,
55 l_t_text TYPE rspc_t_text.
56
57 IF i_dump_at_error = rs_c_true.
58 * ==== Dump at error? => Recursive Call catching errors ====
59 CALL FUNCTION 'RSPC_PROCESS_FINISH'
60 EXPORTING
61 i_logid = i_logid
62 i_chain = i_chain
63 i_type = i_type
64 i_variant = i_variant
65 i_instance = i_instance
66 i_state = i_state
67 i_eventno = i_eventno
68 i_hold = i_hold
69 i_job_count = i_job_count
70 i_batchdate = i_batchdate
71 i_batchtime = i_batchtime
72 EXCEPTIONS
73 error_message = 1.
74 IF sy-subrc <> 0.
>>> MESSAGE ID sy-msgid TYPE 'X' NUMBER sy-msgno
76 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
77 ELSE.
78 EXIT.
79 ENDIF.
80 ENDIF.
81 * ==== Cleanup ====
82 COMMIT WORK.
83 * ==== Get Chain ====
84 IF i_chain IS INITIAL.
85 SELECT SINGLE chain_id FROM rspclogchain INTO l_chain
86 WHERE log_id = i_logid.
87 ELSE.
88 l_chain = i_chain.
89 ENDIF.
90 * ==== Lock ====
91 * ---- Lock process ----
92 DO.
93 CALL FUNCTION 'ENQUEUE_ERSPCPROCESS'
94 EXPORTING
If we do this
Use table RSSDLINIT and in OLTPSOURCRE: enter the name of the data source
And in the logsys enter the name of the source system and delete the entry for that info package. what will happen is process chain will run suceesfully and short dump will not come or what kindly give the detail explanation about this RSSDLINIT.
Regards,
poluru -
BW ERROR while doing data loading
1)while doing data load error--Processing data packet- No Data,
2)Data Package 1 : arrived in BW ; Processing : 2nd processing step not yet finished.
3) Also in some cases there are 0 from 0 records and request is still Yellow i can't delete that too .what option are there to resolve such request.
What can be possible solution.Hi
First the data is come to PSA?If yes then u r problem is from PSA to Data Target.In this case Manually change the request status to red and then delete load the data.
Second If the data not at come to PSA also then check in RSA3 whetehr Data avialble or Not.If it is Delta load then check the entries in RSA7.
Regards
Ram. -
Data load error for master data
hi
both errors i need to fix manually or any automatic is there
psa i need to edit that record and run again infopackage.
i need keep that infoobject(BIC/ZAKFZKZ ) alpha conversion at infoobject level.
Errors in values of the BOM explosion number field:
Diagnosis
Data record 5584 & with the key '001 3000000048420000 &' is invalid in
value 'BOX 55576\77 &' of the attribute/characteristic 0RT_SERIAL &.
InfoObject /BIC/ZAKFZKZ contains non-alpha compliant value 1Hi Suneel,
I feel that the symbol '&' is cauing the issue in ur data loads..
So try to edit the same at the PSA and then load the data from PSa to the target..
Also u can use RSKC to handle these special Chars..
For more information u can search SDN..
Thanks
Hope this helps -
Delta Load Error in the Data Extraction
Hi BI Guru`s,
The issue is with the extractor 2LIS_13_VDKON (Pricing conditions), The regular delta till 22.07.2010 has run successfully, But on 23.07.2010 the delta got failed with the error message " Data Package 58 : arrived in BW ; Processing : Processing not yet finished, entry 70 still missi" for one of the Datapacket. We have repeated the load even though we got the same error message, Since the client is retailer we will be having the delta records of 200 million ( approx. 23369612) in a day. Since because of this error we could't load any of the delta from that day onwards.
Need Help on this:
1. How to get the old delta
2. How to re-initialize the process for delta. (Pls keep it in mind the volume of the records).
Thanks in Advance,
VenkatHi,
Here we need decrease the datapacket size as well as prallel proceesing .
than we need to load the historical data through dalta repetition
hope..helpful for you!
Regards!
Malli. -
Error is Master Data load.
Hi Experts,
From last 1 month the ( 0MAT_UNIT ) master data load is getting failed. Its a full load. So the the target is not updated from last one month( August)
Now the problem is , when I am checking a report. The materials which are new or changed are not getting the data properly. It is because of the master data got stucked at PSA level.And I cant rectify at PSA level because, There is 673 errorneous record in 1 package.
I tried to find the invalid character , but didn't get anything.
Please suggest.
Thanks,
TapuKumarHi Anand,
This is the long text msg
Data records in the PSA were marked for data package 1 . Here there were
673 errors. The system wrote information or warnings for the remaining
data records.
System response
The data package was not updated.
Procedure
Correct the incorrect data records of the data package (for example by
manually editing them in the PSA maintenance). You can find the error
message for each of the records in the PSA by double-clicking on the
status of the record.
Note
Note that you are only allowed to edit and manually update the request
if it is contained in the request list in the data target. Where
necessary, first delete it from the data target.
And it is a master data load( Full ), The data target is a INFO OBJECT.
Please suggest, I can't rectify each and every reecord. Because the number of record id very high..
Thanks,
Tapu Kumar.
Edited by: NewToBW on Sep 2, 2010 1:42 PM -
I can not open my reminders in icloud, error message can't load reminders. Have hp win 8 and all has been fine until today for over a year. win updates are done and itune updates done, what should I do?
Try this - Reset the iPad by holding down on the Sleep and Home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider - let go of the buttons. (This is equivalent to rebooting your computer.) No data/files will be erased.
Cheers, Tom -
Regarding sql function error for Hijri date to Gregorian date
Hi ,
I want to convert Hijri date format into Gregorian date format . i write the script with sql function like this
$Hijri_Date = '16/04/1428';
$Gregorian_Date = sql('DS_REPO','SELECT CONVERT(DATE,[$Hijri_Date],131)');
print($Gregorian_Date);
here $Hijri_Date data type is varchar and $Gregorian_Date data type is date.
but I am getting error like
7868 5812 DBS-070401 10/26/2010 10:37:18 PM |Session Job_Hijradata_Conversion
7868 5812 DBS-070401 10/26/2010 10:37:18 PM ODBC data source <UIPL-LAP-0013\SQLEXPRESS> error message for operation <SQLExecute>: <[Microsoft][SQL Server Native Client
7868 5812 DBS-070401 10/26/2010 10:37:18 PM 10.0][SQL Server]Explicit conversion from data type int to date is not allowed.>.
7868 5812 RUN-050304 10/26/2010 10:37:18 PM |Session Job_Hijradata_Conversion
7868 5812 RUN-050304 10/26/2010 10:37:18 PM Function call <sql ( DS_REPO, SELECT CONVERT(DATE,16/04/1428,131) ) > failed, due to error <70401>: <ODBC data source
7868 5812 RUN-050304 10/26/2010 10:37:18 PM <UIPL-LAP-0013\SQLEXPRESS> error message for operation <SQLExecute>: <[Microsoft][SQL Server Native Client 10.0][SQL
7868 5812 RUN-050304 10/26/2010 10:37:18 PM Server]Explicit conversion from data type int to date is not allowed.>.>.
7868 5812 RUN-053008 10/26/2010 10:37:18 PM |Session Job_Hijradata_Conversion
please help me out to solve this problem .
Please suggest any other solution to convert hijri date format to gregorian date format.
Thanks&Regards,
Ramana.Hi ,
In Data quality there is no inbuild function for converting hijri date to gregorian date . we have the function for converting julian date to gregorian date.
Thanks&Regards,
Ramana.
Maybe you are looking for
-
How to restore my iPhone data after mixed with my husband iTunes
how to restore my iPhone data after mixed with my husband iTunes
-
I tried to erase some of the email addresses that i no longer email to - i went to window to delete some and ALL of them were deleted . How do i get the addresses back? Thank you sooooo much!
-
Can a Windows Hard Drive be reformatted for MAC?
I have a windows computer that I do not use anymore, that I put a 2nd Hard Drive in it. I was wondering if it is possible to install it in my G5 and format it to use it with MAC?
-
ISE/802.1x - IP Conflict at 0.0.0.0?
Has anyone seen this issue? We have Windows 7 clients running 802.1x that will pop up a message in the eventlog that there is an IP conflict with 0.0.0.0. This seems to cause an infinite loop of DHCP NACK and BAD_ADDRESS in the scope. I am on code 1.
-
Hi, I created a new tablespace application and then wanted to create a rollback segment for it by using this command: CREATE ROLLBACK SEGMENT "APPLICATION" TABLESPACE "APPLICATION" STORAGE ( INITIAL 1M NEXT 1M OPTIMAL 4M MINEXTENTS 3 MAXEXTENTS UNLIM