You can disable integrity constraints temporarily so that large amounts of data can be loaded without the overhead of constraint checking. When the data load is complete,you can easily enable the integrity constraints, and you can automatically report any new rows that violate integrity constraints to a separate exceptions table.
鐪嬫潵oracle榪欑偣涓婂仛鐨勬瘮杈冨畬鍠勶紝榪樺彲浠ュ皢榪濆弽瀹屾暣鎬х害鏉熺殑鏁版嵁鑷姩璁板綍鍒頒竴涓猠xception琛ㄤ腑銆?
]]>
鍦╯equential file stage涓湁涓睘鎬у彲浠gnore絎竴琛屻傚浜巉ooter錛屽鏋渇ooter浣跨敤浜嗕笌姝ｆ枃涓嶅悓鐨勬牸寮忥紝鍙互鐢ㄤ嬌鐢╰ransformer stage鍜?@INROWNUM stage鏉ュ皢footer鍘繪帀銆?br>鏂規(guī)硶浜岋細(xì)
鍦╯equential file鐨刦ilter option涓嬌鐢╯ed -e '$d' -e '1d'鏉ヨheader鍜宖ooter鍘繪帀銆?br>鏂規(guī)硶涓夛細(xì)
鍐欎釜before job subroutine錛屽彲浠ュ厛瀵硅繖涓枃浠跺仛鍚勭澶勭悊錛屼笉榪囨垜鎯充篃鏄痵ubroutine涓皟鐢―SExecute sed -e '$d' -e '1d'銆傚綋鐒禕asic涓篃鏈変笓闂ㄥsequential file澶勭悊鐨勫嚱鏁般?br>
]]>
The general callable format is : $orchadmin [options] [descriptor file]
1. Before using orchadmin, you should make sure that either the working directory or the $APT_ORCHHOME/etc contains the file “config.apt” OR
The environment variable $APT_CONFIG_FILE should be defined for your session.
Orchadmin commands
The various commands available with orchadmin are
1. CHECK: $orchadmin check
Validates the configuration file contents like , accesibility of all nodes defined in the configuration file, scratch disk definitions and accesibility of all the nodes etc. Throws an error when config file is not found or not defined properly
2. COPY : $orchadmin copy
Makes a complete copy of the datasets of source with new destination descriptor file name. Please not that
a. You cannot use UNIX cp command as it justs copies the config file to a new name. The data is not copied.
b. The new datasets will be arranged in the form of the config file that is in use but not according to the old confing file that was in use with the source.
3. DELETE : $orchadmin <> [-f -x] descriptorfiles….
The unix rm utility cannot be used to delete the datasets. The orchadmin delete or rm command should be used to delete one or more persistent data sets.
-f options makes a force delete. If some nodes are not accesible then -f forces to delete the dataset partitions from accessible nodes and leave the other partitions in inaccesible nodes as orphans.
-x forces to use the current config file to be used while deleting than the one stored in data set.
4. DESCRIBE: $orchadmin describe [options] descriptorfile.ds
This is the single most important command.
1. Without any option lists the no.of.partitions, no.of.segments, valid segments, and preserve partitioning flag details of the persistent dataset.
-c : Print the configuration file that is written in the dataset if any
-p: Lists down the partition level information.
-f: Lists down the file level information in each partition
-e: List down the segment level information .
-s: List down the meta-data schema of the information.
-v: Lists all segemnts , valid or otherwise
-l : Long listing. Equivalent to -f -p -s -v -e
5. DUMP: $orchadmin dump [options] descriptorfile.ds
The dump command is used to dump(extract) the records from the dataset.
Without any options the dump command lists down all the records starting from first record from first partition till last record in last partition.
-delim ‘’ : Uses the given string as delimtor for fields instead of space.
-field : Lists only the given field instead of all fields.
-name : List all the values preceded by field name and a colon
-n numrecs : List only the given number of records per partition.
-p period(N) : Lists every Nth record from each partition starting from first record.
-skip N: Skip the first N records from each partition.
-x : Use the current system configuration file rather than the one stored in dataset.
6. TRUNCATE: $orchadmin truncate [options] descriptorfile.ds
Without options deletes all the data(ie Segments) from the dataset.
-f: Uses force truncate. Truncate accessible segments and leave the inaccesible ones.
-x: Uses current system config file rather than the default one stored in the dataset.
-n N: Leaves the first N segments in each partition and truncates the remaining.
7. HELP: $orchadmin -help OR $orchadmin -help
Help manual about the usage of orchadmin or orchadmin commands
]]>
4 鍛戒護(hù)琛屽彲浠ユ墽琛屻佸鍏ob絳夛紝瀹冮氳繃dsjob瀹炵幇錛屽湪DS Manager鐨勬枃妗ｄ腑榪樿浜嗘湁涓撻棬鐨勫懡浠よ鏉ュ鍏ob
5 鍙互緙栧啓shell鏉ユ帶鍒秊ob錛屽dsjob鍛戒護(hù)鍋氬皝瑁咃紝鍙互浼犲叆鍙傛暟絳夈?br>瀵逛簬涓婇潰榪欎簺姒傚康榪樻槸寰堟ā緋婏紝鍏堣褰曞湪姝ゃ?
]]>
]]>
################################################################################
#######
####### FILE: MasterControl.ksh
#######
####### DESCRIPTION: Starts a DataStage MasterControl type job passing
####### all runtime parameter values
#######
#######
####### Date Version Developer Description
####### ---------- --------- -------------- ------------------------------------
####### 2002-05-15 1.0 Ken Bland Initial release
####### 2002-06-27 2.2 Ken Bland FileSetDate/ProcessDate modifications
####### 2002-07-10 2.2 Steve Boyce Added ProcessDate as 14th parameter
####### 2002-08-16 2.3 Steve Boyce Now calls stored procedure
####### GET_NEW_BATCH_NBR in datastage schema
####### instead of deriving it and inserting
####### here.
####### Uses comSQLPlus.ksh and comPLSQL.ksh
####### instead of SQLPlusStub.ksh.ksh
#######
PROG=`basename ${0}`
EXIT_STATUS=0
NOW=`date`
echo "${NOW} ${PROG} Initialization..."
echo
#######
####### CONFIGURATION ##########################################################
#######
if [ ${#} -ne 14 ]; then
echo "${NOW} ${PROG} : Invalid parameter list."
echo "${NOW} ${PROG} : The script needs 14 parameters:"
echo "${NOW} ${PROG} : JobName"
echo "${NOW} ${PROG} : ParameterFile"
echo "${NOW} ${PROG} : FileSetDate (YYYY-MM-DD)"
echo "${NOW} ${PROG} : BatchNumber"
echo "${NOW} ${PROG} : JobHierarchyFile"
echo "${NOW} ${PROG} : SourceSystemList"
echo "${NOW} ${PROG} : SubjectAreaList"
echo "${NOW} ${PROG} : ClearWorkArea"
echo "${NOW} ${PROG} : StartingMilestone"
echo "${NOW} ${PROG} : EndingMilestone"
echo "${NOW} ${PROG} : DebugMode"
echo "${NOW} ${PROG} : JobLinkStatisticChecksFile"
echo "${NOW} ${PROG} : ResurrectLogFile"
echo "${NOW} ${PROG} : ProcessDate (NULL|YYYY-MM-DD H24:MI:SS)"
exit 99
fi
JobName="${1}"
ParameterFile="${2}"
FileSetDate="${3}"
BatchNumber="${4}"
JobHierarchyFile="${5}"
SourceSystemList="${6}"
SubjectAreaList="${7}"
ClearWorkArea="${8}"
StartingMilestone="${9}"
EndingMilestone="${10}"
DebugMode="${11}"
JobLinkStatisticChecksFile="${12}"
ResurrectLogFile="${13}"
ProcessDate="${14}"
echo "${NOW} ${PROG} JobName ${JobName}"
echo "${NOW} ${PROG} ParameterFile ${ParameterFile}"
echo "${NOW} ${PROG} FileSetDate ${FileSetDate}"
echo "${NOW} ${PROG} BatchNumber ${BatchNumber}"
echo "${NOW} ${PROG} JobHierarchyFile ${JobHierarchyFile}"
echo "${NOW} ${PROG} SourceSystemList ${SourceSystemList}"
echo "${NOW} ${PROG} SubjectAreaList ${SubjectAreaList}"
echo "${NOW} ${PROG} ClearWorkArea ${ClearWorkArea}"
echo "${NOW} ${PROG} StartingMilestone ${StartingMilestone}"
echo "${NOW} ${PROG} EndingMilestone ${EndingMilestone}"
echo "${NOW} ${PROG} DebugMode ${DebugMode}"
echo "${NOW} ${PROG} JobLinkStatisticChecksFile ${JobLinkStatisticChecksFile}"
echo "${NOW} ${PROG} ResurrectLogFile ${ResurrectLogFile}"
echo "${NOW} ${PROG} ProcessDate ${ProcessDate}"
echo
# Below will look in the parameters.ini file to determine the directory path each.
UserID=`whoami`
BinFileDirectory=`cat /.dshome`/bin
LogFileDirectory=`grep -w LogFileDirectory ${ParameterFile}|cut -d "=" -f2`
TempFileDirectory=`grep -w TempFileDirectory ${ParameterFile}|cut -d "=" -f2`
CommonScriptFileDirectory=`grep -w CommonScriptFileDirectory ${ParameterFile}|cut -d "=" -f2`
CommonLogFileDirectory=`grep -w CommonLogFileDirectory ${ParameterFile}|cut -d "=" -f2`
LogFileName=${CommonLogFileDirectory}/${PROG}_${JobName}.log
TEMPBATCHNBRLOG=${TempFileDirectory}/${PROG}_${JobName}_start.log
DATASTAGEPROJECT=`grep -w DATASTAGEPROJECT ${ParameterFile}|cut -d "=" -f2`
DSSERVER=`grep -w DSSERVER ${ParameterFile}|cut -d "=" -f2`
DSUSERID=`grep -w DSUSERID ${ParameterFile}|cut -d "=" -f2`
DSPASSWORD=`grep -w DSPASSWORD ${ParameterFile}|cut -d "=" -f2`
NOW=`date`
echo "${NOW} ${PROG} UserID ${UserID}"
echo "${NOW} ${PROG} BinFileDirectory ${BinFileDirectory}"
echo "${NOW} ${PROG} LogFileDirectory ${LogFileDirectory}"
echo "${NOW} ${PROG} TempFileDirectory ${TempFileDirectory}"
echo "${NOW} ${PROG} CommonScriptFileDirectory ${CommonScriptFileDirectory}"
echo "${NOW} ${PROG} CommonLogFileDirectory ${CommonLogFileDirectory}"
echo "${NOW} ${PROG} LogFileName ${LogFileName}"
echo "${NOW} ${PROG} TEMPBATCHNBRLOG ${TEMPBATCHNBRLOG}"
echo "${NOW} ${PROG} DATASTAGEPROJECT ${DATASTAGEPROJECT}"
echo "${NOW} ${PROG} DSSERVER ${DSSERVER}"
echo "${NOW} ${PROG} DSUSERID ${DSUSERID}"
echo "${NOW} ${PROG} DSPASSWORD *Protected*"
echo
#######
####### PARAMETER BUILD Without batch number ##################################
#######
if [ "${ProcessDate}" = "NULL" ]; then
StartTimestamp=`date '+%Y-%m-%d %H:%M:%S'`
else
StartTimestamp="${ProcessDate}"
fi
ParamList=" -param ParameterFile=${ParameterFile}"
ParamList="${ParamList} -param ProcessDate=\"${StartTimestamp}\""
ParamList="${ParamList} -param FileSetDate=${FileSetDate}"
ParamList="${ParamList} -param JobHierarchyFile=${JobHierarchyFile}"
ParamList="${ParamList} -param SourceSystemList=${SourceSystemList}"
ParamList="${ParamList} -param SubjectAreaList=${SubjectAreaList}"
ParamList="${ParamList} -param ClearWorkArea=${ClearWorkArea}"
ParamList="${ParamList} -param StartingMilestone=${StartingMilestone}"
ParamList="${ParamList} -param EndingMilestone=${EndingMilestone}"
ParamList="${ParamList} -param DebugMode=${DebugMode}"
ParamList="${ParamList} -param JobLinkStatisticChecksFile=${JobLinkStatisticChecksFile}"
ParamList="${ParamList} -param ResurrectLogFile=${ResurrectLogFile}"
#######
####### Get Batch Number and create ETL_BATCH_AUDIT record #####################
#######
echo "${NOW} ${PROG} About to get new BATCH_NBR and insert it into ETL_BATCH_AUDIT..."
${CommonScriptFileDirectory}/comPLSQL.ksh ${ParameterFile} "IRDSN" "IRUserID" \
GET_NEW_BATCH_NBR \
"${JobName}" \
"${StartTimestamp}" \
"${UserID}" \
"${SourceSystemList}" \
"${SubjectAreaList}" \
"${ParamList}" \
"${FileSetDate}" > ${TEMPBATCHNBRLOG}
SQL_EXIT_STATUS=$?
cat ${TEMPBATCHNBRLOG}
if [ "${SQL_EXIT_STATUS}" != 0 ]; then
NOW=`date`
echo "${NOW} ${PROG} Failure to connect/insert into ETL_Batch_Audit table!"
exit ${SQL_EXIT_STATUS}
fi
#######
####### Get BATCH_NBR from batch number log file ##############################
#######
BatchNumber=`grep -w BATCH_NBR ${TEMPBATCHNBRLOG}|cut -d "=" -f2`
if [ -z "${BatchNumber}" ]; then
NOW=`date`
echo "${NOW} ${PROG} Failure to retrieve BATCH_NBR from ${TEMPBATCHNBRLOG}"
exit ${SQL_EXIT_STATUS}
fi
#######
####### Add batch number to list of parameters #################################
#######
ParamList="${ParamList} -param BatchNumber=${BatchNumber}"
NOW=`date`
echo
echo ${NOW} ${PROG} Parameter list: ${ParamList}
echo
#######
####### DataStage EXECUTION ####################################################
#######
NOW=`date`
echo "${NOW} ${PROG} Executing DataStage dsjob program..."
echo ${BinFileDirectory}/dsjob -server ${DSSERVER} -user ${DSUSERID} -password ${DSPASSWORD} -run -wait ${ParamList} ${DATASTAGEPROJECT} ${JobName} 2>&1 > ${LogFileName}
echo
echo "${BinFileDirectory}/dsjob -server ${DSSERVER} -user ${DSUSERID} -password ${DSPASSWORD} -run -wait ${ParamList} ${DATASTAGEPROJECT} ${JobName} 2>&1 > ${LogFileName}"
echo
eval ${BinFileDirectory}/dsjob -server ${DSSERVER} -user ${DSUSERID} -password ${DSPASSWORD} -run -wait ${ParamList} ${DATASTAGEPROJECT} ${JobName} 2>&1 >> ${LogFileName}
jobwaiting=`grep "Waiting for job..." ${LogFileName}`
if [ "${jobwaiting}" != "Waiting for job..." ]; then
NOW=`date`
echo ${NOW} ${PROG} "DataStage failed to start the job"
failedstart=1
else
NOW=`date`
echo ${NOW} ${PROG} "DataStage successfully started the job"
failedstart=0
fi
NOW=`date`
echo ${NOW} ${PROG} "Retrieving job information"
${BinFileDirectory}/dsjob -server ${DSSERVER} -user ${DSUSERID} -password ${DSPASSWORD} -jobinfo ${DATASTAGEPROJECT} ${JobName} >> ${LogFileName}
#######
####### CHECK STATUS ###########################################################
#######
ERROR=`grep "Job Status" ${LogFileName}`
ERROR=${ERROR##*\(}
ERROR=${ERROR%%\)*}
if [ "${failedstart}" != 0 ]; then
NOW=`date`
echo ${NOW} ${PROG} "The job failed to start"
AuditStatus="FAILURE"
Comments="MasterControl aborted"
EXIT_STATUS=1
else
if [ "${ERROR}" = 1 -o "${ERROR}" = 2 ]; then
NOW=`date`
echo ${NOW} ${PROG} "The job completed successfully"
AuditStatus="SUCCESS"
Comments=""
EXIT_STATUS=0
else
NOW=`date`
echo ${NOW} ${PROG} "The job aborted"
AuditStatus="FAILURE"
Comments="MasterControl aborted"
EXIT_STATUS=1
fi
fi
FailedJobCount=`grep -i FAILED ${LogFileDirectory}/${JobName}.log|wc -l|cut -b1-9`
FailedJobCount=`expr ${FailedJobCount} + 0`
echo ${NOW} ${PROG} The number of failed jobs is [${FailedJobCount}]
if [ "${FailedJobCount}" != 0 ]; then
NOW=`date`
echo ${NOW} ${PROG} "The job had failed processes"
AuditStatus="FAILURE"
Comments="MasterControl had ${FailedJobCount} failed processes"
EXIT_STATUS=1
fi
StoppedJobStreamCount=`grep "JOB STREAM STOPPED" ${LogFileDirectory}/${JobName}.his|wc -l|cut -b1-9`
StoppedJobStreamCount=`expr ${StoppedJobStreamCount} + 0`
if [ "${StoppedJobStreamCount}" != 0 ]; then
NOW=`date`
echo ${NOW} ${PROG} "The job stream was STOPped or KILLed"
AuditStatus="FAILURE"
Comments="MasterControl job stream was STOPped or KILLed"
EXIT_STATUS=1
fi
#######
####### AUDIT ##################################################################
#######
echo
echo "${NOW} ${PROG} About to update ETL_BATCH_AUDIT with status information..."
EndTimestamp=`date '+%Y-%m-%d %H:%M:%S'`
SQLstring="UPDATE ETL_BATCH_AUDIT A \
SET A.END_TIMESTAMP = TO_DATE('${EndTimestamp}','YYYY-MM-DD HH24:MI:SS'), \
A.STATUS = '${AuditStatus}', \
A.COMMENTS = '${Comments}', \
A.RUNTIMESETTINGS = '${ParamList}' \
WHERE (A.BATCH_NBR = ${BatchNumber});"
NOW=`date`
echo ${NOW} ${PROG} Audit SQL ${SQLstring}
SQLScriptFileName=${TempFileDirectory}/${PROG}_${JobName}_end.sql
echo ${SQLstring} > ${SQLScriptFileName}
${CommonScriptFileDirectory}/comSQLPlus.ksh ${ParameterFile} IRDSN IRUserID ${SQLScriptFileName}
SQL_EXIT_STATUS=$?
if [ "${SQL_EXIT_STATUS}" != 0 ]; then
NOW=`date`
echo ${NOW} ${PROG} Failure to connect/update into ETL_Batch_Audit table!
exit ${SQL_EXIT_STATUS}
fi
#######
####### EXIT ###################################################################
#######
NOW=`date`
echo ${NOW} ${PROG} Complete, exiting with status [${EXIT_STATUS}]
exit ${EXIT_STATUS}
濂戒笢瑗匡紝鍏堟敹鐫錛屽啀鐮旂┒銆?/span>
]]>
Error calling subroutine: DSR_EXECJOB (Action=1); check DataStage is set up correctly in project ETUDES
(Subroutine failed to complete successfully (30107))
+
(40503) A call to an OLE server has failed, or a runtime error occured within the ole itself.
瑙ｅ喅鍔炴硶錛?br>1 棣栧厛榪愯鍛戒護(hù)錛欴ELETE FROM DS_JOBS WHERE NAME = 'JobName'
2 鍐嶈繍琛孌S.CHECKER 錛屾敞鎰忚榪愯DS.CHECKER蹇呴』瑕佹湁exclusive access鍒皃roject
錛岄氳繃濡備笅鍛戒護(hù)鍙互鐪嬪埌鏈夎皝榪樿繛鎺ュ埌浜嗘湇鍔″櫒錛歯etstat -a |grep dsrpc
]]>
1 涓鑸殑BASIC紼嬪簭鏄涓嬩竴涓牸寮?br>[ label ] statement [ ; statement … ] <Return>
2 鍏充簬subroutine
a 濡傛灉宓屽叆鍒頒簡紼嬪簭涓敤GOSUB璋冪敤錛屽鏋滃湪澶栭儴錛屼嬌鐢–ALL
b 浣跨敤return榪斿洖鍒頒富紼嬪簭錛屽鏋滃湪return涔嬪墠subroutine緇撴潫浜嗭紝鑷姩return
c 濡傛灉subroutine涓湁ABORT STOP CHAIN鍒欐案榪滃洖涓嶅埌涓葷▼搴忋?br>3 娉ㄩ噴
浠EM * ! $* 寮澶寸殑涓烘敞閲?br>4 鍒涘緩涓涓狟ASIC 紼嬪簭鐨勬楠?br>浣跨敤CREATE.FILE鍛戒護(hù)鍒涘緩涓涓猼ype 1鎴杢ype 19 DataStage file鏉ヤ繚瀛楤ASIC紼嬪簭鐨勬簮鐮併?鍦―SEngine鐩綍涓嬭繍琛孋REATE.FILE鍛戒護(hù)錛屽畠?yōu)畣鎻惤C轟綘杈撳叆鏂囦歡鍚嶇瓑鍙傛暟)
浣跨敤DataStage Editor鎴栧叾浠栫紪杈戝櫒鍒涘緩BASIC紼嬪簭婧愮爜錛岃繖涓簮鐮佹垚涓轟綘鍒氭墠鍒涘緩鐨勬枃浠剁殑涓鏉¤褰曘?/p>
浣跨敤BASIC鍛戒護(hù)鏉ョ紪璇戜綘紼嬪簭錛岃繖灝嗗垱寤轟竴涓寘鍚洰鏍囦唬鐮佺殑鏂囦歡銆傜洰鏍囨枃浠剁殑鍚嶅瓧涓嶉噸瑕侊紝鍥犱負(fù)鎬繪槸閫氳繃婧愭枃浠跺悕鏉ュ紩鐢ㄧ▼搴忋?/p>
鍙互鐢≧UN鍛戒護(hù)鏉ユ墽琛屼綘鐨勭▼搴忥紝浣跨敤RAID鍛戒護(hù)鏉ヨ皟璇曚綘鐨勭▼搴忋?/p>
浜屻佸熀紜鐭ヨ瘑
鏁版嵁綾誨瀷銆佸彉閲忓拰鎿嶄綔絎?br>鎵鏈夋暟鎹湪鍐呴儴閮芥槸浠ュ瓧絎︿覆瀛樺偍錛屽湪榪愯鏃惰漿鎹負(fù)鍏蜂綋綾誨瀷銆?br>涓昏鏈変笁縐嶆暟鎹被鍨嬶細(xì)瀛楃涓層佹暟瀛楀瀷銆佸拰unknown錛坣ull錛?/p>
瀛楃涓?br>鍦˙ASIC婧愮爜涓紝瀛楃涓蹭駭閲忔槸ASCII瀛楃鐨勫簭鍒楋紝鎵浠ヤ笉鑳芥湁0錛坣ull錛夊拰10錛坙inefeed錛夊瓧絎︼紝鑰屾槸瑕佷嬌鐢–HAR(0)鍜孋HAR(10)
鏁板瓧鍨?br>鑼冨洿浠?0(-307)鍒?0(307)錛屾渶澶?5浣嶅皬鏁?br>unknown
null鍦ㄥ唴閮ㄦ槸鐢卞崟涓瀛楄妭CHAR(128)浠ｈ〃鐨勶紝鏄竴涓猻tring錛屽彲浠ョ敤緋葷粺鍙橀噺@NULL.STR鏉ュ紩鐢ㄥ畠銆傚湪BASIC紼嬪簭涓彲浠ヤ嬌鐢ㄧ郴緇熷彉閲廆NULL鏉ュ紩鐢╪ull鍊箋?br>涓涓瓧絎︿覆涓巒ull榪炴帴緇撴灉涓簄ull
鏁扮粍
dimensioned array
鍦ㄥ悜閲忥紙涓緇存暟緇勶級涓紝絎竴涓厓绱犵殑index涓?
鍚戦噺鍙互鐪嬪仛絎簩浣嶄負(fù)1鐨勪簩緇存暟緇勶紙鐭╅樀錛夈?br>鐭╅樀鍜屽悜閲忕殑絎竴涓厓绱犲垎鍒敤vector.name(0)鍜宮atrix.name(0,0)琛ㄧず銆傚畠鍙互鍦∕ATPARSE銆丮ATREAD鍜孧ATWRITE璇彞涓敤鏉ュ瓨鍌ㄤ笉鍚堟牸鐨勫瓧孌點(diǎn)?/p>
鍔ㄦ佹暟緇?br>鍔ㄦ佹暟緇勭殑鏈楂樺眰鏄瓧孌碉紝鐢?F)鍒嗗壊銆傚瓧孌靛寘鍚湁(V)鍒嗗壊鐨勫肩粍鎴愩傛瘡涓煎張鍙互鍖呭惈鐢?S)鍒嗗壊鐨剆ubvalue銆?/p>
瀛楃涓茬殑姣旇緝
瀛楃涓茬殑姣旇緝鏄竴涓釜鐨勬瘮杈冩瘡涓瓧絎︾殑ASCII鐨勫箋傚鏋滀袱涓瓧絎︿覆鍙互杞崲涓烘暟瀛楋紝鎬繪槸姣旇緝涓や釜鏁板瓧鐨勬暟鍊煎ぇ灝忋備換浣曞間笌null鐩告瘮杈冪殑緇撴灉閮芥槸unknown銆傜┖涓蹭笉鏄畝鍗曠殑絳変簬0銆傜┖鏍肩湅鍋氬皬浜?銆?/p>
瀛楃涓插尮閰?br>X浠ｈ〃浠諱綍瀛楃 A浠ｈ〃鎵鏈夊瓧姣?N浠ｈ〃鎵鏈夋暟瀛?鍓嶉潰鐨勬暟瀛椾唬琛ㄩ噸澶嶆鏁般傚鏋滃墠闈㈢殑鏁板瓧涓?錛屼唬琛ㄥ悗闈㈢殑瀛楃閲嶅0鍒癗嬈＄殑浠繪剰嬈℃暟閮藉彲浠ャ?/p>
0鏄痜alse 絀轟覆鏄痜alse null闈瀟rue闈瀎alse
閿?浜嬪姟鍜岄殧紱葷駭鍒?br>閿?br>閿佹湁涓ょ綺掑害錛氱粏綺掑害錛堣褰曢攣瀹氾級鍜岀矖綺掑害錛堟枃浠墮攣瀹氾級
DataStage鏀寔浠ヤ笅鍑犵閿侊細(xì)
璁板綍鍏變韓閿?br>璁板綍鏇存柊閿?br>鏂囦歡鍏變韓閿?br>鏂囦歡鎰忓悜錛坕ntent錛夐攣 浠嬩簬鍏變韓涓庢帓浠栦箣闂?br>鏂囦歡鎺掍粬閿?/p>
浜嬪姟
浜嬪姟鍙互宓屽
瀛愪簨鍔″湪鐖朵簨鍔℃彁浜ゆ垨鍥炴粴涔嬪墠寮濮嬬殑璇濓紝瀛愪簨鍔″皢鍙樻垚媧誨姩浜嬪姟錛岃岀埗浜嬪姟灝嗙戶緇瓨鍦ㄤ絾鏄槸闈炴椿鍔ㄧ殑銆傚綋瀛愪簨鍔℃彁浜ゆ垨鍥炴粴涔嬪悗錛岀埗浜嬪姟灝嗗啀嬈″彉涓烘椿鍔ㄧ殑銆?br>鍦ㄦ渶楂樺眰鐨勪簨鍔℃彁浜や箣鍓嶏紝灝嗙紦瀛樻墍鏈夊瓙浜嬪姟鐨勬暟鎹簱鎿嶄綔銆傚綋榪涜涓涓鍙栨搷浣滄椂錛岄鍏堜細(xì)鍘昏鍙栫紦瀛樼殑鏁版嵁錛屽鏋滄壘涓嶅埌鎵嶄細(xì)浠庢暟鎹簱鏂囦歡涓鍙栥?br>
]]>
MProperties.IDB_PASS + " " + MProperties.DS_PROJECT + " " + MProperties.DS_JOB);
p.waitFor();
return p.exitValue() == 0;
鍙﹀濡傛灉鏈塕TI錛屾洿濂界殑鏂規(guī)硶濡備笅錛?/span>
The best way for this to be accomplished is by using the RTI (Real Time Integration) capabilities that we added in 7.x. This allows you to fully expose a DataStage job as a service, to be then invoked via several different mechanisms, depending on your needs....
.....the job can be exposed as a classic web service, using SOAP over HTTP...we generate and publish the WSDL for this within RTI...
....the job can be exposed via our EJB binding and called appropriately
....the job can be exposed for contact via JMS, and either passed a text message or SOAP envelope....
Not only can you simply pass job parameters via this architecture, you can actually have the entire transformation job itself (columns on the ultimate input and output links) passed and returned to your calling client.
Additionally, the entire job control API, which you may already be familiar with in its API or command line implementations, has been exposed as a set of methods available via Web Services.
涓昏灝辨槸閫氳繃灝唈ob鍖呰涓簑eb service鎴朎JB鎴朖MS鏉ヨ皟鐢紝鍙互浼犲弬鏁幫紝榪樺彲浠ュ皢鏁翠釜job鏈韓錛堟渶緇堢殑杈撳叆鍜岃緭鍑洪摼鎺ワ級浣滀負(fù)鍙傛暟浼犻掓垨鑰呰繑鍥炲埌璋冪敤鐨勫鎴風(fēng)銆?
]]>
榧犳爣鍙抽敭鐐瑰嚮璧峰stage錛屾寜浣忓彸閿Щ鍔ㄩ紶鏍囧埌鐩爣stage銆傝繕鏈変竴縐嶆柟娉曞氨鏄妸榧犳爣鏀懼湪璧峰stage鐨勮竟緙樼瓑鍒板彉涓轟竴涓皬鍦嗗湀閲岄潰鏈変竴涓弶鐨勬椂鍊欐嫋鍔ㄩ紶鏍囧埌鐩爣stage銆?br>
DataStage涓粯璁ゅ拰闅愬紡綾誨瀷杞崲鏃舵敞鎰忕殑闂
褰撲粠婧愬悜鐩爣鏄犲皠鏁版嵁鏃訛紝濡傛灉綾誨瀷涓嶄竴鑷達(dá)紝瀵逛簬鏈変簺綾誨瀷鎴戜滑闇瑕佸湪modify鎴杢ransfomer stage涓氳繃鍑芥暟榪涜杞崲錛屽浜庢湁浜涚郴緇熶細(xì)鑷姩瀹屾垚綾誨瀷杞崲錛屽湪綾誨瀷杞崲榪囩▼涓紝娉ㄦ剰浠ヤ笅鍑犵偣錛?br>1 鍦ㄥ彉闀垮埌鍥哄畾闀垮害瀛楃涓茬殑榛樿杞崲涓紝parallel jobs鐢ㄧ┖鏍鹼紙ASCII 20錛夊瓧絎︽潵濉厖鍓╀綑闀垮害銆傝仈緋誨埌鍓嶉潰鍋氱殑涓涓猵arallel job錛屽綋鐩爣鏄彉闀挎椂錛堝綋鏃舵簮涔熸槸鍙橀暱錛屼絾鏄ソ鍍忔簮鐨勭簿搴﹁灝忎簺錛夛紝浣嗘槸瀛楃涓插疄闄呯殑闀垮害娌℃湁鎸囧畾鐨勫彉闀塊偅涔堥暱鐨勮瘽錛岀郴緇熶細(xì)鑷姩鐢ㄧ┖鏍鹼紙ASCII 20錛夋潵濉厖錛堝叿浣撳湪鍝釜stage濉厖鐨勪笉鐭ワ級錛岃屼笖鐜鍙橀噺APT_STRING_PADCHAR鐨勯粯璁ゅ間篃鏄┖鏍鹼紙ASCII 20錛夈?br>2 閫氳繃鐜鍙橀噺APT_STRING_PADCHAR鍙互鏀瑰彉榛樿鐨勫～鍏呭瓧絎ull錛圓SCII 0錛夛紝鍚屾椂涓鑸繕瑕佸姞涓妕rim灝辮兘瑙ｅ喅絀烘牸闂錛屾闂闈炲父鏅亶銆?br>3 鏈変釜PadString 鍑芥暟鍙互鐢ㄦ潵鐢ㄦ寚瀹氱殑瀛楃鏉ュ～鍏呬竴涓彉闀跨殑瀛楃涓插埌鎸囧畾鐨勯暱搴︺傝繖涓嚱鏁扮殑鍙傛暟涓嶈兘浣垮浐瀹氶暱搴﹀瓧絎︿覆錛屽鏋滄槸鍥哄畾闀垮害鐨勫厛杞寲涓哄彉闀褲?br>
Copy Stage浣滀負(fù)鍗犱綅絎?/strong>
鍦╦ob寮鍙戜腑錛屽綋浣犳殏鏃朵笉鐭ラ亾璇ヤ嬌鐢ㄥ摢涓猻tage鏃訛紝鍙互浣跨敤copy stage浣滀負(fù)鍗犱綅絎︼紝娉ㄦ剰涓嶈鎶奆orce灞炴ц涓篢rue錛屽湪涓嶆妸Force璁句負(fù)True鏃訛紝澶嶅埗灝嗗湪榪愯鏃惰繘琛屼紭鍖栥?br>
浣跨敤Schema file鏉ユ寚瀹歮eta data
1 鍙互閫氳繃鍒楀畾涔夊拰schema file涓ょ鏂瑰紡鏉ユ寚瀹歮eta data錛屽煎緱娉ㄦ剰鐨勪竴鐐規(guī)槸Note that, if you use a schema file, you should ensure that runtime column propagation is turned on. Otherwise the column definitions specified in the stage editor will always override any schema file.鍗籌紝濡傛灉鎯抽氳繃schema file鏉ユ寚瀹歮eta data錛屽繀欏誨嬀涓妑untime column propagation錛屽惁鍒欐繪槸浣跨敤鍒楀畾涔夋潵浣滀負(fù)meta data銆?
2 If you are using a schema file on an NLS system, the schema file needs to be in UTF-8 format.濡傛灉浣犵殑datastage浣跨敤浜哊LS system錛岄偅涔坰chema file蹇呴』鏄疷TF-8鏍煎紡鐨勩傛枃妗ｄ腑璇村彲浠ヤ嬌鐢⊿equential stage鏉ュ畬鎴愯漿鐮併?br>
閫氳繃Server Shared Container鍦≒arallel Job涓坊鍔燬erver Job Stage
You create a new shared container in the DataStage Designer, add Server job stages as required, and then add the Server Shared Container to your Parallel job and connect it to the Parallel stages.鍦―esigner涓垱寤轟竴涓猻erver shared container錛屾坊鍔犻渶瑕佺殑Server job stage錛屽啀鎶妔erver shared container娣誨姞鍒皃arallel job騫惰繛鎺ュ埌鍏朵粬parallel stage銆?br>
鍑犱釜鐜鍙橀噺鐨勫叿浣撹礬寰?/span>
%SERVERENGINE% – DataStage engine account directory(normally C:\Ascential\DataStage\Engine on Windows and <dsadminhome>\Ascential\DataStage\DSEngine on UNIX).
%PROJECT% – Current project directory.
%SYSTEM% – System directory on Windows NT or /usr/lib on UNIX.
涓鍙ヤ笉澶噦鐨勮瘽錛屽厛鍋氳褰?/span>
If NLS is enabled, avoid using the built-in Iconv and Oconv functions to map data unless you fully understand the consequences of your actions.鍦ㄤ嬌鐢ㄤ簡NLS鏃訛紝灝介噺閬垮厤浣跨敤Iconv and Oconv鏉ユ槧灝勬棩鏈燂紝鍥犱負(fù)鍙兘浜х敓涓浜涙剰鎯充笉鍒扮殑緇撴灉銆?br>
]]>