Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. jlaw10

    Need to automate "incremental" SQL Loader process

    I meant that the external table has not been created yet. So do I need the unique field added to the flat file prior to setting up the external table?
  2. jlaw10

    Need to automate "incremental" SQL Loader process

    Also the source flat file has the following data. What is the best way to add the primary key ID field to the external table in this case? Also, do I need to add a comma to separate the fields? data.2011082020_15 20110820223605 00:00:19 9008 474.105 data.2011082020_16...
  3. jlaw10

    Need to automate "incremental" SQL Loader process

    Was thinking of using the minus operation to identify new rows.
  4. jlaw10

    Need to automate "incremental" SQL Loader process

    Ok good idea. I think I can use external loader and load data using SQL Loader. Any recommendation on how to avoid loading duplicate data since the new data will just be appended to the flat file?
  5. jlaw10

    Need to automate "incremental" SQL Loader process

    I have a quick task to setup a job to load data directly into database from flat files. I was going to use SQL Loader. Attached are the two sample data files. 1st priority is with the log.par file. I need to set up a process where both of these get loaded into the database on a continuous basis...
  6. jlaw10

    user sudo fails ("Sorry, user temp1 is not allowed to execute")

    I am receiving the following errors when attempting to setup sudo from user A (temp1) to user B (oracle): Sorry, user temp1 is not allowed to execute '/bin/su - oracle' as root host1 This happens with the following sudoers entry: temp1 ALL=(oracle) NOPASSWD:ALL This works only when I change...
  7. jlaw10

    Database State Weekly Status Report Template

    Looking for a good DB state weekly status report template. We want something that also business level can understand. Report should include: * Top Issues * Recommended Resolutions * Top SQL * etc Graphs and chart format would be good. Thanks!
  8. jlaw10

    Protect Linux root or user history log

    Thanks to all for the great advice! I have also read that enable Process Accounting. Is this best practice? If so what is the best way to keep this file size down. I have heard pros/cons against logrotate for the pacct file.
  9. jlaw10

    Protect Linux root or user history log

    Thanks for the great input. Is there a way to list out the past root logins? (i.e. root logins over past 30 days). Or is this info captured in a file anywhere?
  10. jlaw10

    Protect Linux root or user history log

    Looking for the recommended way to protect the root and user history logs. We had an instance where a user logged in as root and then ran malicious commands but then deleted the trace of these commands. What is the best way to prevent this? Also, is there a way to print/report for example who...
  11. jlaw10

    Linux Host Security Scan Tool

    I need to scan and confirm security compliance for a RedHat Linux Server. I want to capture such items as the following: - open ports - review suid, sgid - user password security scan - privileged user scan - scan for availability of critical files - overall compliance scan Is there a free...
  12. jlaw10

    audit/log root login history and commands

    Thanks for the comment. The "set | grep -i history" command lists the history file location and I am able to see the commands within the history file. I need to take it a step further by listing which user runs which commands as root (also timestamps if possible).
  13. jlaw10

    audit/log root login history and commands

    I need to follow best practice for logging daily root login activity as well as commands executed as root user. What is the recommended method? We are implementing tighter security on one of our Prod Enterprise Linux boxes.
  14. jlaw10

    errors using 'who' command

    Annihilannic...the email output is perfect just one small detail and then this issue will be closed. I still received this error at at the command line (despite email results as expected): [root@prematics32 ~]# ) -bash: syntax error near unexpected token `)'
  15. jlaw10

    errors using 'who' command

    Still receive same errors w/ all recommended options: [root@prematics31 ~]# echo 'ALERT - Root Shell Access on:' `date` `who` mail -s "Alert: Root Access from `who cut -d -f1`" jason.outlaw@micoresolutions.com who: invalid option -- f Try `who --help' for more information. ALERT - Root Shell...
  16. jlaw10

    errors using 'who' command

    Attempting to monitor root access w/ the following command - http://adminlinux.blogspot.com/2007/10/system-security-monitor-root-access.html: [root@prematics32 ~]# echo 'ALERT - Root Shell Access on:' `date` `who` mail -s "Alert: Root Access from `who cut -d"(" -f2 cut -d")" -f1`"...
  17. jlaw10

    Red Hat Linux mysterious reboots

    I actually just got more info stating that this Linux server is running on a VMWare cluster of six Dell R905s. No other servers are having an issue. There are about 150 VM client servers on the cluster. They also moved the Linux server from one VM cluster mate to another but the reboots...
  18. jlaw10

    Red Hat Linux mysterious reboots

    Would a bad batter or power failure reflect the "shutting down for system reboot" message in the logs?
  19. jlaw10

    Red Hat Linux mysterious reboots

    A client had a 3 day span where their Red Hat server reboot several times throughout the day. We did not see any cronjobs or anything that stood out in the alert logs that would've caused the reboots. The system logs are attached. Client still seeking cause of reboot eventhough we have not seen...
  20. jlaw10

    maintenance plans best practices on system DBs

    I have a SQL 2000/2005 instance and am setting up maintenance plans. I was told that is best to only do maintenance plans (update stats, shrink DBs, rebuild indexes, etc) on User DBs. Should these also be periodically run on system DBs?

Part and Inventory Search

Back
Top