1/30/2023 0 Comments Grep only file time![]() ORA-39151: Table "WKSYS"."WK$_SOURCE_GROUP" exists. All dependent metadata and data will be skipped due to table_exists_action of skip ORA-39111: Dependent object type TRIGGER:"SYSMAN"."SPACE_METRICS_PURGE_TRIGGER" skipped, base object type VIEW:"SYSMAN"."MGMT_SPACE_PURGE" already exists ORA-39111: Dependent object type TRIGGER:"SYSMAN"."SEV_ANNOTATION_DELETE_TR" skipped, base object type VIEW:"SYSMAN"."MGMT_SEVERITY_ANNOTATION" already exists ORA-39111: Dependent object type TRIGGER:"SYSMAN"."SEV_ANNOTATION_INSERT_TR" skipped, base object type VIEW:"SYSMAN"."MGMT_SEVERITY_ANNOTATION" already exists Grep exact match In our examples above, whenever we search our document for the string apple, grep also returns pineapple as part of the output. ORA-31684: Object type TABLESPACE:"TEMP" already exists grep Sstring filename This command tells grep to be case sensitive except for the first letter. ORA-31684: Object type TABLESPACE:"SYSAUX" already exists ![]() ORA-31684: Object type TABLESPACE:"UNDOTBS1" already exists > cat import.log | grep ORA-39082 | wc -l Now, every day at 10am grep command will search data.txt for test string and append the output to result.txt file. 0 10 sudo grep 'test' /home/data.txt > /etc/result.txt Save and close the file. > cat import.log | grep ORA-29357 | wc -l crontab -e Add the following line to run the above grep command every day at 10 am. > cat import.log | grep ORA-39083 | wc -l I did the following workaround to prune the ORA-39151 grep ORA-39111 grep ORA-31684 redirecting the output to another file then search with the same for ORA- patternĬat full_import.log | grep -v -e ORA-39151 -e ORA-39111 -e ORA-31684 >import.log Using pipes we send the output of a command to grep and use it to search for patterns / keywords. > cat full_import.log | grep ORA-31684 | wc -līut there are 42 Error still missing. The strongest use case for grep is when it is paired with another command. > cat full_import.log | grep ORA-39111 | wc -l If this option is used multiple times or is combined with the -e ( -regexp) option, search for all patterns given. f FILE, -fileFILE Obtain patterns from FILE, one per line. > cat full_import.log | grep ORA-39151 | wc -l This option can be used to protect a pattern beginning with. Lets say, for example, you wanted to find every occurrence of the words bee and Vanessa in a text document containing the script from the 2007 Bee movie. I went through the file and found some errors and did simple word count command This syntax, using the and /, followed by the location of the file in the home folder, is what youll use to show the grep command which files to search. The log file ends with "Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 3384 error(s) at 11:38:14" which shows that we have 3384 error in the log file ![]() I had some manual analysis and workarounds to find out the errors however it consumes time and i am sure there are more easier way. So I am looking for a way to list the distinct errors. I have a huge import log file and it's too hard to review the full log file to verify all reported errors are ignorable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |