Emacs Dired rename many files

[From]: http://stackoverflow.com/questions/15881776/emacs-dired-rename-many-files

This can easily be done using dired:

  1. Enter a dired view of your directory
  2. Switch to writable dired mode (wdired-change-to-wdired-mode): C-xC-q
  3. Edit the file names listing as if it were a normal buffer (for example using a keyboard macro or a rectangular selection or query-replace). Here is a regexp-based solution:

    C-M-%\(VAR.\)_\(..\)RET\2_\1RET

  4. Finish editing (wdired-finish-edit): C-xC-s or C-cC-c

You’re done!

shareedit

How can I change the date modified/created of a file?

[From]: http://askubuntu.com/questions/62492/how-can-i-change-the-date-modified-created-of-a-file

Easiest way – accessed modified will be the same:

touch -a -m t 201512180130.09 fileName.ext

Where:

-a = accessed
-m = modified
t  = timestamp - use [[CC]YY]MMDDhhmm[.ss] time format

If you wish to use NOW just drop the t and the timestamp

To verify they are all the same: stat fileName.ext

See: touch man

shareimprove this answer

Run an Oracle package from SQL Server Integration Services

[From]: https://www.mssqltips.com/sqlservertip/2724/run-an-oracle-package-from-sql-server-integration-services/

Problem

An Oracle Package is similar to a SQL Server SQL Server Stored Procedure. If you want to run an Oracle Package and then execute a web service, copy files or folders, a sequence of tasks, etc. you may need to use SQL Server Integration Services (SSIS). SSIS is a powerful tool included with SQL Server to integrate data from different databases. Typically, the Oracle Package sequences are created in the Oracle Warehouse Builder, but sometimes we need to combine Oracle code with some Microsoft tasks. In this case, SSIS is a viable option.  So in this tip we will show you how to call an Oracle Package from an SSIS Package.

Solution

In the first example, we are going to run an Oracle package without parameters in SQL Server Integration Services. The second example will run a package with parameters.

Requirements

  • I am assuming that you already know how to create a connection to Oracle. If you do not, read this tip – Export SQL Server Data to Oracle using SSIS.
  • You need to have SSIS and Oracle installed.  In my case I tested SQL Server 2012 with the Oracle client 11g, but the examples in this tip should work with earlier versions.
  • You need to have some Oracle packages already created. If you do not know how to create Oracle packages, refer to this link:Oracle packages.

Getting Started with calling an Oracle Package from SQL Server Integration Services

In this example, we are going to run the following Oracle package with the Execute SQL Task:

BEGIN PKG_EMPE_DIM.ETL_ALL_EMPE_DIM;
END;

Lets start an Integration Services project with the SQL Server Data Tools (SSDT) in SQL Server 2012 or the Business Intelligence Development Studio (BIDS) in SQL Server 2008 or 2005:

  1. Create a connection to your Oracle server.
    connections
  2. In the Control Flow tab drag and drop the Execute SQL Task. This task let’s us execute SQL tasks to Excel, OLE DB providers, ADO.NET providers and ODBC. You can connect to mySQL, Oracle, Postgres, etc. database with this powerful task.
    connections
  3. Double click on the Execute SQL Task and select the connection to Oracle which you already created.
    Open the SQL Server Management Studio
  4. Double click on the SQLStatement ellipsis and write the following code:
    BEGIN PKG_EMPE_DIM.ETL_ALL_EMPLE_DIM;
    END;
    
    Backup the Multidimentional Database
  5. In the example above, the package name is PKG_EMPE_DIM.ETL_ALL_EMPLE_DIM. The BEGIN, semicolons and END are very important in Oracle.
  6. That is all! If you run the SSIS package, by pressing the green play button, the Oracle package will be executed.
    Save the file as
  7. The package status can be verified in the Progress tab as shown below.
    Save the file as

 

Running an Oracle Package from SSIS with parameters

You can also pass parameters from SSIS to the Oracle Package.

In this example we are going to run the following package with these parameters:

BEGIN TRCKNG_FCT.ETL_STG_AR_ADTNL_TRCKNG_FACT('20120501','20120501','N','D');
END;

Now, if you want to run a package with parameters, you need to add a few items to the existing SSIS package we just created:

  1. On the Control Flow tab, double click on the Execute SQL Task then click on the SQLStatement ellipsis in order to modify the code being issued.
    Specify the backup path and options
  2. In the “Enter SQL Query” text box, write the package name and use the question mark for the parameters. In this example this package has 4 parameters.
    Save the script in a different path.
  3. I am using SQL Server 2012, I will go to the parameters tab to work with the variables. If you are using earlier versions of SSIS, go to the SSIS menu and click Variables.
  4. Add the needed parameters (variables) with the correct data types.  In my scenario the parameters are varchars so I am using the string data type. You also need to add the parameter values.
    Script Action to New Query Window

    The following table maps the SSIS and Oracle data types:

    Oracle Data Types

    SSIS Parameter Data Types

    RAW byte
    date datetime
    TIMESTAMP, DATE, INTERVAL datetime
    NUMBER, INT Int16, Int32, Int64
    FLOAT, REAL float
    CHAR, VARCHAR2, NVARCHAR2, NCHAR string
  5. Now, with the Execute SQL Task, we need to go to the Parameter Mapping interface to map the question marks parameters created in step 3.  Here is the interface:
    Save the file as
  6. I chose the parameters in the Parameter Mapping interface. The first question mark in step 2 above belongs to parameter name0, the second question mark belongs to the second which is parameter name 1 and so on. In this example the Data Type is nvarchar. The parameter name is very important here. For more information about parameter and OLEDB click here.  Keep in mind that OLEDB provider uses numbers as a parameter names. The first parameter is named 0 and the second 1 and so on.  Other providers like ODBC do not use numbers as parameter names.
  7. The following table will help you to map SSIS variables in the Parameter Mapping interface in the Execute SQL Task:
    SSIS Parameter Data Types

    Execute SQL Task parameter mapping data types

    byte BYTE
    datetime DB_DATE
    Int16, Int32, Int64 LONG
    float FLOAT
  8. Finally, you have your package ready to run with the parameters.   Press the green play button.
    Save the file as
  9. In order to see the results, you can setup log files in SSIS. To configure this feature click on the package’s control flow tab, then select the SSIS menu and the Logging option. In the interface below select the option for “SSIS log provider for Text files” and review the log once the execution is complete.
    log ssis
  10. Additionally, you can also configure error handling using the Event Handler Tab. We will explain more details about error handling and SSIS logging in future tips:
    log ssis

 

As a final note, keep in mind the parameters in this example were configured with specific values for design time testing.  To pass parameters into an SSIS Package at runtime, you can use the DTEXEC command to run the SSIS package with the required parameters.

Additional SSIS Functionality

Keep in mind you can execute Oracle procedures, packages and functions with SSIS and combine them with other tasks like sending email or the file system task to extend the functionality of your packages. In future tips we will cover these topics in more detail.

Save the file as
Next Steps

Powershell ps1 file “is not recognized as a cmdlet, function, operable program, or script file.”

http://stackoverflow.com/questions/762927/powershell-ps1-file-is-not-recognized-as-a-cmdlet-function-operable-program

This is a typical error across many platforms where your environment path does not include your current directory. so when you execute your script (or command or program etc), your runtime environment looks everywhere except your current/working directory.

Try

PS> .\listAllPaths.ps1 c:\ *.pdf testingPDF.txt

EDIT: After reading your comments, I’m going to suggest you try this. I haven’t actually verified the logic of your PS script. I’m merely trying to get your script to execute first.

Try editing your script as below, and execute as above.

Function listAllPaths([string]$fromFolder, [string]$filter, [string]$printfile){
Get-ChildItem -Path $fromFolder -Include $filter -Recurse -Force -Name > $printfile
}

listAllPaths
shareedit

PowerShell says “execution of scripts is disabled on this system.”

[From:] http://stackoverflow.com/questions/4037939/powershell-says-execution-of-scripts-is-disabled-on-this-system

773down voteaccepted

If you’re using Windows 2008 R2 then there is an x64 and x86 version of PowerShell both of which have to have their execution policies set. Did you set the execution policy in both hosts?

You can set the execution policy by typing this into your powershell window:

Set-ExecutionPolicy RemoteSigned

For more information see here.

shareedit

How can I configure the Command Prompt to display French correctly?

[From:] http://superuser.com/questions/332109/how-can-i-configure-the-command-prompt-to-display-french-correctly

Try “PowerShell ISE” not “PowerShell” – it understands UTF-8 and other character sets.

enter image description here


Update:

Problem

You are seeing Ú instead of é

Analysis

é is at code point 0xE9 in ISO 8859-1 Latin-1 (and several similar encodings)
Ú is at code point 0xE9 in code page 850

Therefore your application is emitting text using Latin-1 encoding. However your console is set for code page 850.

Solution

Using chcp to change the console encoding will, in conjunction with an appropriately encoded font, most likely solve the problem.


I can reproduce the problem and fix it by changing the command prompt properties to change the font from “Raster” to “Lucida Console”. The Raster fonts have what Microsoft refer to as an OEM encoding.

before

after

shareimprove this answer

Try changing the code page with the chcp command. For example:

C:\ chcp 1252

I say 1252 because this guy seemed to have success with it for displaying French characters.

If that works there is still another step because it is reset with every command prompt window. I haven’t tested this out but according to this site it will change the code page for all future command prompt windows.

Start->Run->regedit
Go to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage]
And change the "OEMCP" value to "1252"

chcp command found on ComputerHope.com

shareimprove this answer