timestamp « WordPress.com Tag Feed

HISTTIMEFORMAT: add execution time to Linux's history file

Mohammed — Sat, 07 Nov 2009 08:32:23 +0000

As you might know, Linux logs all the commands executed on a shell prompt to its history file. The f

How to get Current Date and Time in SQL

zaheedk — Tue, 27 Oct 2009 10:43:59 +0000

Ever wondered that how can I get the current Date and Time in SQL, just the way we dot in VB.Net using Date.now. Well it is more simple than you thought

Use T-SQL command CURRENT_TIMESTAMP

This will return the current date and time value without the database time zone offset.

How do i use it? It’s very simple……

Select CURRENT_TIMESTAMP (returns the current date and time)

Update table1 set ddate = CURRENT_TIMESTAMP (updates table1 and sets value of field ddate to current date and time)

Hope you find this article useful….

Is your physical model "XML ready"?

stefanoravec — Mon, 26 Oct 2009 14:02:23 +0000


drop table t;
drop view v;
create table t (t timestamp);
insert into t values (current_timestamp);
commit;
create view v as select xmlforest(t) x from t;

alter session set nls_language='AMERICAN';
alter session set nls_territory='AMERICA';
select * from v;
X
-------------------------------------------
2009-10-26T14:51:58.916436


alter session set nls_language='CZECH';
alter session set nls_territory='CZECH REPUBLIC';
select * from v;

Error report:
SQL Error: ORA-01877: pro vnitřní vyrovnávací paměť je řetězec příliš dlouhý
01877. 00000 -  "string is too long for internal buffer"
*Cause:    This is an internal error.
*Action:   Please contact Oracle Worldwide Support.


truncate table t;
alter table t modify(t timestamp with local time zone);
insert into t values (current_timestamp);
commit;

alter session set nls_language='CZECH';
alter session set nls_territory='CZECH REPUBLIC';
select * from v;
X
-------------------------------------------
2009-10-26T14:51:59.086511+01:00


alter session set nls_language='AMERICAN';
alter session set nls_territory='AMERICA';
select * from v;

X
-------------------------------------------
2009-10-26T14:51:59.086511+01:00

jQuery Plugin: It's CuteTime!

Jeremy Horn — Mon, 26 Oct 2009 13:45:07 +0000

Many online social products, and more continue to, avoid a formal timestamp format…

2009-10-10 23:14:17 and Thu, October 29, 2004 12:14:19 PM

… opting for more user friendly, “warm and fuzzy,” human-readable styles…

9 days ago and 5 years ago.

As a result, and also in my quest to always help provide my clients free, cheap and easy to use tools, I have been on the lookout for a jQuery plugin that would provide the ability to easily…

convert timestamps to ‘cuter’ language-styled forms (e.g. yesterday, 2 hours ago, last year, in the future!),
customize the time scales and output formatting, and
dynamically update the displayed CuteTime(s) upon request and/or automatically.

While there are other similar tools out there in JavaScript, PHP, and, I am sure, many other languages, none adequately met my goals. Therefore, I created the jQuery CuteTime plugin.

Usage

CuteTime is a customizable jQuery plugin (jQuery.cuteTime) that automatically converts timestamps to formats much cuter. Also, it has the ability to dynamically re-update and/or automatically update timestamps on a controlled interval.

As a Function

If used as a function, a string containing a cuteTime version of the provided timestamp is returned.

$(document).ready(function () {
	// timestamp MUST be a valid Date().parse 'able' format
	$.cuteTime('2009/10/12 22:11:19');
});

<html>
	<body>
		<div class='predetermined'></div>
	</body>
</html>

As a Method

If used via Selector, CuteTime replaces the text of the provided object with a cuteTime.

$(document).ready(function () {
	$('.timestamp').cuteTime();
});

<html>
	<body>
		<div class="timestamp">
			2009/10/12 22:11:19
		</div>
		<div class="timestamp">
			2008/11/01 07:11:00
		</div>
		<div class="timestamp">
			2018/11/01 07:11:00
		</div>
		<div class="timestamp"></div>
		<div class="timestamp" cutetime="1980/10/12 22:11:19">
			2009/10/12 22:11:19
		</div>
		<div class="timestamp" cutetime="asd">
			10/12/2009 22:11:19
		</div>
		<div class="timestamp" cutetime="asd">
			aoisd
		</div>
		<div class="timestamp" cutetime="asd"></div>
	</body>
</html>

When initialized, the cuteTime() call either updates or assigns the ‘cutetime’ attribute to the provided objects. Method implementation supports chaining, returning the jQuery object.

e.g. <div class=’timestamp’ cutetime=’2009 10 12 22:11:19′>2009 10 12 22:11:19</div>

If the cutetime attribute already exists within the provided object, then the text within the object is ignored in the cutification process. If the cutetime attribute does not exist or an invalid one is provided, then a valid cutetime attribute is assigned to the object.

If the cutetime attribute is missing, then it is calculated from the text of the provided object.

If neither cutetime attribute nor valid object text exist, then the timestamp is assumed to be ‘now’.

When using CuteTime in the form…

<br />
$(document).ready(function () {
	remember_the_cuteness = $('.timestamp').cuteTime();
});

… the following methods can be used …

// stops all automatic updates of refresh-enabled timestamps
remember_the_cuteness.stop_cuteness();

// (re)starts the automatic updating of timestamps
// REMINDER: make sure refresh is set to > 0
remember_the_cuteness.start_cuteness();

// updates timestamps of the provided objects
remember_the_cuteness.update_cuteness();

Settings

By default, automatic updating is disabled and the following CuteTimes can be displayed…

the future!
just now
a few seconds ago
a minute ago
x minutes ago
an hour ago
x hours ago
yesterday
x days ago
last month
x months ago
last year
x years ago

To change these settings, they can either be accessed directly…

$.fn.cuteTime.settings.refresh = 10000;

… or at the time of initialization …

my_cutetime = $('.timestamp_move').cuteTime({ refresh: 60000*10 });

The default settings data structure is…

$.fn.cuteTime.settings = {
	refresh: -1,			// time in milliseconds before next refresh of page data; -1 == no refresh
	time_ranges: [
		{bound: NEG_INF,	// IMPORANT: bounds MUST be in ascending order, from negative infinity to positive infinity
			cuteness: 'the future!',			unit_size: 0},
		{bound: 0,
			cuteness: 'just now',				unit_size: 0},
		{bound: 20 * 1000,
			cuteness: 'a few seconds ago',		unit_size: 0},
		{bound: 60 * 1000,
			cuteness: 'a minute ago',			unit_size: 0},
		{bound: 60 * 1000 * 2,
			cuteness: ' minutes ago',			unit_size: 60 * 1000},
		{bound: 60 * 1000 * 60,
			cuteness: 'an hour ago',			unit_size: 0},
		{bound: 60 * 1000 * 60 * 2,
			cuteness: ' hours ago',				unit_size: 60 * 1000 * 60},
		{bound: 60 * 1000 * 60 * 24,
			cuteness: 'yesterday',				unit_size: 0},
		{bound: 60 * 1000 * 60 * 24 * 2,
			cuteness: ' days ago',				unit_size: 60 * 1000 * 60 * 24},
		{bound: 60 * 1000 * 60 * 24 * 30,
			cuteness: 'last month',				unit_size: 0},
		{bound: 60 * 1000 * 60 * 24 * 30 * 2,
			cuteness: ' months ago',			unit_size: 60 * 1000 * 60 * 24 * 30},
		{bound: 60 * 1000 * 60 * 24 * 30 * 12,
			cuteness: 'last year',				unit_size: 0},
		{bound: 60 * 1000 * 60 * 24 * 30 * 12 * 2,
			cuteness: ' years ago',				unit_size: 60 * 1000 * 60 * 24 * 30 * 12},
		{bound: POS_INF,
			cuteness: 'a blinkle ago',			unit_size: 0}
	]
};

The parameters are defined (and all can be overridden) thus…

refresh
- time in milliseconds before next refresh of page data;
- a value of -1 disables refreshing

time_ranges
- the array of bound_structures that delineate the cute descriptions associated with time_ranges
- time_range’s boundary structures consist of the following variables…

time_range[x].bound
- the value is an integer representing the time difference between the provided timestamp and now
- the lower inclusive bound, or starting point, for using the ‘cuteness’ string that describes the current timestamp
- the exclusive upper bound is defined by the next boundary structure definition in the time_ranges array [current boundary + 1]

time_range[x].cuteness
- string to use in place of the current timestamp (e.g. ‘yesterday’)

time_range[x].unit_size
- the integer divisor in milliseconds to apply to the calculated time difference
- if unit_size > 0 then a number value is prepended to the cuteness string as calculated by time_difference / unit_size (e.g. 4 hours ago)
- if unit_size = 0, then no number is prepended to the cuteness string (e.g. an hour ago)

BTW

Make sure you use timestamps that are fully recognized by the JavaScript Date object’s Parse method in all the IE and FF browser versions you want to support. Otherwise, prepare for a headache.

Get It

You can download CuteTime, dual licensed under GPL and MIT, from…

jQuery Repository
http://plugins.jquery.com/project/CuteTime

Git
Public Clone URL: git://github.com/theproductguy/CuteTime.git
GitHub: http://github.com/theproductguy/CuteTime

Zip
jQuery.cuteTime_source-bundle_1.0_20091019.zip

Demo

http://theproductguy.com/cutetime/cutetime.demo.html

Status updates can be found here, jQuery CuteTime.
If you find this useful, or have any questions, ideas, or issues, leave a comment.

Enjoy!

Jeremy Horn
The Product Guy

Add to Social Bookmarks:

Linux Rename using Modified Date

Neil Obremski — Thu, 22 Oct 2009 20:50:20 +0000

I know I’m going to forget how I did this again, especially if I lose the following script I wrote, so I’m posting it here. Here’s the gist: a directory full of files and I want to to copy them to a new location while also changing them to lower-case, using a different extension (MOD => mpg), and finally including the Last Modified date in the name (YYMMDD-hhmmss).

#! /bin/bash
for file in $1/*.MOD
do
   modifdate=`stat -c %y $file`
   formatdate=`date -d "$modifdate" "+%Y%m%d-%0k%M%S"`
   echo "cp -p -u $file $2/mov-$formatdate.mpg"
   cp -p -u $file $2/mov-$formatdate.mpg
done

Note to myself: you called it movcp and put it in /usr/bin. Thus I go from this …

Raw video files from SD card for my Canon FS100

Using this …

Linux script copying files off Canon FS100 SD and adding timestamp to their name.

To this:

Canon FS100 files are just MPEG-2 without proper aspect ratio header set

Voila! Now I can archive these off to my ReadyNAS and online backup.

Change in behavior in Timestamp.valueOf() in JDK 6

Vijay Dev — Wed, 21 Oct 2009 17:56:43 +0000

Recently, when looking at a bug related to Timestamp, I found out that the valueOf() method in java.sql.Timestamp works differently in JDK 6 than the earlier versions.

Timestamp.valueOf(), when provided with a timestamp which contains a date or a month with a single digit. eg. 2009-9-20, 2009-9-3, 2009-12-4 etc., behaves differently in JDK 6 – it throws an IllegalArgumentException saying that the timestamp is not properly formatted. Whereas JDK 5 (and earlier versions) works just fine providing the proper values with ‘0′ prefixed to those single digit numbers. However JDK 6 is fine with hours, minutes, seconds being single digits. As usual, got curious and started exploring why this happens by looking at the source code for the Timestamp class in JDK 5 and 6.

Here’s the JDK 6 Timestamp.valueOf() snippet:

int counterD = 0;
int intDate[] = {4,2,2};

int counterT = 0;
int intTime[] = {2,2,12};

while(stringTokeninzerDate.hasMoreTokens()) {
String tokenDate = stringTokeninzerDate.nextToken();
if(tokenDate.length() != intDate[counterD] ) {
throw new java.lang.IllegalArgumentException(formatError);
}
counterD++;
}

/*
//Commenting this portion out for checking of time

while(stringTokeninzerTime.hasMoreTokens()) {
String tokenTime = stringTokeninzerTime.nextToken();

if (counterT < 2 && tokenTime.length() != intTime[counterT] ) {
throw new java.lang.IllegalArgumentException(formatError);
}
counterT++;
}
*/

The code in bold shows that there is a strict check on the length of the digits that constitute the datepart of the timestamp. The commented out source is the reason why the format of the digits in the time part is not strictly enforced.

I thought it’s good to dig more into this and asked in Stack Overflow and people helped out in identifying more details: The behaviour is already filed as a bug and more info about the bug was found here. A workaround for this problem is available here.

Dates in PHP & MySQL

Mr Chimp — Thu, 01 Oct 2009 11:37:37 +0000

It took me a while to get my head around usign dates in PHP and MySQL but it’s actually quite simple. I’m not sure what order to talk about this in so I’ll just go ahead and ramble.

NOW()
The MySQL NOW() function can be used in an SQL string to insert the current date and time into a field. Like this:

INSERT INTO dates (the_date) VALUES (NOW())

Pretty straight forward but very useful. Of course you can also set the “on update CURRENT_TIMESTAMP” option in MySQL so that any time the record is altered the timestamp will be updated with the current time. This is useful for “last modified” attributes on things like blog posts.

Timestamps
Timestamps are the number of seconds since a given time. Unix timestamps are the number of seconds since 01-01-1970 00:00:00. They’re good for computers but basically unreadable by humans.

Some of PHPs date functions take a timestamp as an argument so while they’re a little confusing and you’re bound to need them at some point.

Personally I think a nicely formatted string like “20091001124212″ could make life a whole lot easier but there’s reasons why it doesn’t work like that, so just get used to timestamps!

mktime()
PHP Manual Page – W3Schools Page

An easy way to make a timestamp is the mktime (aka MaKe TIMEstamp) function in PHP. The basic syntax is as follows:

mktime(hour, min, sec, month, day, year[, is_dst])

It’s pretty straight forward, just stick the appropriate numbers in one end and a timestamp falls out the other. The is_dst means “is daylight saving time” which should be used if your PHP version is less than 5.

You can do date addition/subtraction with this function, too. For example:
mktime(0, 0, 0, date("m"), date("d")+100, date("y"))
would give you a timestamp for 100 days in the future.

NOTE:
Mktime() will spazz out if you give it values with leading zeros. For example the year 09 would be interpreted as 0. The solution? Make sure you don’t use leading zeros. For the year value, try to use four digit numbers to avoid ambiguity.

date()
PHP Manual Page – W3Schools Page
The date() function formats a date/time in the format of your choice. It takes one or two arguments: date($format_string[, $timestamp]). If $timestamp is not given the current time is used. The format string is made up of special characters, each of which denotes a way of displaying the hour or minute or month etc. For example ‘d/m/y’ would give you (at the time of writing) 01/10/09. A complete list of available special characters follows:

d – Day of month (01 – 31)
D – Day as text (three letters)
j – Day of month, no leading zeros (1 to 31)
l (lowercase ‘L’) – Day, full text
N – The ISO-8601 numeric representation of a day (1 for Monday through 7 for Sunday)
S – The English ordinal suffix for the day of the month (2 characters st, nd, rd or th. Works well with j)
w – A numeric representation of the day (0 for Sunday through 6 for Saturday)
z – The day of the year (from 0 through 365)
W – The ISO-8601 week number of year (weeks starting on Monday)
F – A full textual representation of a month (January – December)
m – month number (01 – 12)
M – A short textual representation of a month (jan – dec)
n – Month number no leading zeros (1 to 12)
t – The number of days in month
L – Leap year (1 if leap year, 0 otherwise)
o – The ISO-8601 year number
Y – Year, four digits (2009)
y – A two digit representation of a year (09)
a – Lowercase am or pm
A – Uppercase AM or PM
B – Swatch Internet time (000 to 999)
g – 12-hour hour (1 to 12)
G – 24-hour hour (0 to 23)
h – 12-hour hour (01 to 12)
H – 24-hour hour (00 to 23)
i – Minutes, leading zeros (00 to 59)
s – Seconds, leading zeros (00 to 59)
e – The timezone identifier (Examples: UTC, Atlantic/Azores)
I (capital i) – Daylights savings time (1 if Daylight Savings Time, 0 otherwise)
O – Difference to Greenwich time (GMT) in hours (Example: +0100)
T – Timezone setting of the PHP machine (Examples: EST, MDT)
Z – Timezone offset in seconds. The offset west of UTC is negative, and the offset east of UTC is positive (-43200 to 43200)
c – The ISO-8601 date (e.g. 2004-02-12T15:19:21+00:00)
r – The RFC 2822 formatted date (e.g. Thu, 21 Dec 2000 16:01:07 +0200)
U – The seconds since the Unix Epoch (January 1 1970 00:00:00 GMT)

strtotime()
This PHP function takes a string written in normal English and attempts to convert it into a timestamp. For example:

strtotime('next Thursday');
strtotime('+7 hours');
strtotime('+1 week');

On failure function returns false on PHP5 and -1 on earlier versions.

——————————————————-
For a full list of PHP date/time functions check out the w3schools page.

DBA_HIST_DATABASE_INSTANCE

Amin Jaffer — Wed, 30 Sep 2009 04:12:30 +0000

In 10g there is a view called DBA_HIST_DATABASE_INSTANCE which has database instance information. It

Timestamp your Notepad

Swetha Sankaran — Tue, 08 Sep 2009 19:01:18 +0000

Create a blank text file in Notepad
Type .LOG in the first line of the file.
Press ENTER(carriage return)
Save the file with any name of your choice.
Open the file again and notice the time stamp at the top.

Converting Perfmon timestamps to a readable format in Excel

Julie — Thu, 06 Aug 2009 19:13:40 +0000

I have been using Microsoft’s Performance Monitor (perfmon) to capture data that hopefully allow me to understand the I/O bottleneck my Windows 2003 R2 server is experiencing only occasionally.

I’ve saved this data as a .csv file, and import it into Excel so I can analyze the raw data. The problem is, the timestamp column is in some indecipherable format that doesn’t map to actual time.

I did some playing around with the cell formating in Excel, and this is how I was able to get the Perfmon timestamp displayed in a usable format. I’m using Excel 2002 in this example, so you may need to adapt the instructions to your environment.

1. Import the Perfmon .csv file into Excel

2. Right click the timestamp column, which is column A for me

3. Select Format Cells

4. On the Number tab, select Custom Category

5. In the Type box, enter the following:

MM/dd/yyyy hh:mm:ss

Note there is a space between the yyyy and hh

Press OK, and your time stamp column should now be in a human readable format!

Entity Framework: TimeStamp fields not recognized for optimistic concurrency model

Syed Mehroz Alam — Wed, 05 Aug 2009 10:53:51 +0000

Today, while working with Entity Framework, I noticed through SQL Profiler that my update queries were not using timestamp field. I looked into my model and found that my timestamp fields have Concurrency Mode property set to None. It was quite strange; The entity model was auto generated and I wonder why the EF designer could not identify my timestamp field (I remember Linq To SQL designer automatically took care of such fields). Anyway, I changed Concurrency Mode to Fixed and it worked great. So, as a final note, when generating entity model from database, don’t forget to set appropriate concurrency modes for your timestamp fields as it is not done by the designer itself.

Añadir timestamp al nombre de un fichero mediante Java mapping

tykall — Tue, 28 Jul 2009 12:51:24 +0000

En el siguiente código se muestra cómo añadir el timestamp al nombre de un fichero a través de una UDF (User-Defined Function) mediante acceso a las variables del sistema.

DynamicConfiguration conf = (DynamicConfiguration) container
 .getTransformationParameters()
 .get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);

DynamicConfigurationKey key = DynamicConfigurationKey.create(
 "http:/"+"/sap.com/xi/XI/System/File",
 "FileName");

String FileName = filename[0];
String addTS = addTimestamp[0];
String TS;
java.util.Map map;
// get runtime constant map
map = container.getTransformationParameters();
// get value of header field
TS = (String) map.get(StreamTransformationConstants.TIME_SENT);

if(addTS.equals("X")){
 FileName = FileName + ".backup-" + TS;
};

conf.put(key, FileName);
result.addValue(FileName);

Como variables de entrada tenemos el nombre del fichero y un indicador (addTimestamp) para decidir si hay que incluir el timestamp o no.

Enlaces de referencia:

touch - modyfikacja czasu dostępu do pliku, tworzenie plików

sylwekb — Tue, 21 Jul 2009 19:57:46 +0000

Cześć,

Teraz zaprezentuje Państwu polecenie touch. Jak wynika za samego tytułu wpisu polecenie to ma służyć do zmiany daty modyfikacji pliku, ale również dzięki temu poleceniu możemy tworzyć nowe pliki.

Składnia polecenia jest następująca:

touch [opcje] plik

Postaram się teraz przybliżyć bardziej przydatne opcje:

-m – zmienia czas modyfikacji pliku

-c – nie powoduje utworzenia nowego pliku

-d data – skutkuje ustawieniem daty przyjętym w parametrze, a nie czas obecny, format daty jest następujący rrrrmmdd (r rok, m miesiąc, d dzień)

-t data - tutaj jest używany podobnie jak w przypadku opcji d czas podany w parametrze data zamiast czasu obecnego. Z tym, że w odróżnieniu od opcji d jest inny format czasu: [[RR]RR]MMDDhhmm[.ss] (h godzina, m minuta, s sekundy)

-r plik_wzorcowy – możny również do zmiany daty modyfikacji pliku użyć pliku wzorcowego

Z opisu teoretycznego to było by na tyle więc przyszedł czas na przykłady:

touch plik1 – spowoduje utworzenie pliku o nazwie plik1

touch -d 20090125 plik1 – spowoduje utworzenie pliku o nazwie plik1 i datą 25 stycznia 2009 roku. Jeżeli taki plik istnieje zostanie zmieniony czas modyfikacji pliku

touch -c -d 20091224 plik2 – tutaj zaistniała sytuacja podobna do przykładu wyżej, ale jeżeli plik o nazwie plik2 nie istnieje to wówczas nie zostanie on utworzony

touch -m plik* – nastąpi zmiana czasu modyfikacji (dla wszystkich plików zwierających na początku nazwy treść “plik”) na czas obecny

To wszytko co miało dotyczyć polecenia touch. Zachęcam do przeczytania podręcznika man lub info. (polecenie man touch, info touch)

Linux: Timestamp conversion methods

Mohammed — Fri, 26 Jun 2009 03:34:13 +0000

A timestamp is a sequence of characters, denoting the date and/or time at which a certain event occu

Tips: Where Did the Time Go? D6 and the UTC Timestamp

Pie — Sat, 20 Jun 2009 02:29:14 +0000

I had planned to start running all of my “Tips” posts in the EMC Developer Network, but I wanted to editorialize a little in this Tip, so I’ve decided to throw it up here. This issue arose when I installed a new repository into an existing environment. It is a documented issue, though the Support guys need to read that documentation a little more closely.

The Time Warp

As you may have guessed from the title, I recently ran into an issue regarding the Timestamp in the Documentum Content Server. We were looking at an update to a system and we noticed that the times in our little Data Shack were wrong, by about 5 hours. We looked in the source Audit Trail in Documentum and we saw that both the time_stamp field and the time_stamp_utc field in the dm_audittrail_s table had the same value.

I had the team open a case with EMC Support and they quickly got nowhere.

After a few days, and a little thought, I browsed through some documentation and found this nugget in the Content Server Administration Guide:

By default, date values are stored as follows:

As UTC (Coordinated Universal Time) time in new repositories (Documentum 6 and later).

As the Content Server’s local time in repositories that are upgraded from before version 6.

This made sense. We had rebuilt our development repository recently to clean it up, and so the date handling had changed. Mystery solved! Time to call it a day?

No.

The problem was that in every other environment, there was an existing repository that already handled dates in local time. The plan was to create a new repository for a specialized type of content. That repository would have the new rule, but the repository dates wouldn’t match, making reporting a little nightmarish.

Support had told us that everything was working as intended and closed the case without so much as a by-your-leave. My thought was that if two repositories running the same version of the software can behave in two different manners, there has to be a flag. The Administration Guide mentioned a field titled r_normal_tz. What was this field and where was it?

So the search was on. After a bit of digging, a support note was uncovered. Support Note #98383, Dates stored in Content Server V6.0 original install incorrectly calculate UTC time component offset in storing dates. Does not occur if content server was upgraded from 5.3 to 6.0, explained how the setting could be changed. The value is in stored the docbase_config object. The documentation says that the field should not be changed if the value is not 0. I tend to agree with this assessment as it will probably throw things out of synch.

Lucky for me, the problem was that the field was set to 0. I just had to issue a simple DQL (Update dm_docbase_config Object Set r_normal_tz = -18000) to update the value for the Eastern Time Zone (-5*60*60 as the value store the differential in seconds). This value was also confirmed in the existing repositories. After the change, we just had to restart the repository.

Wallah! It worked and now all is well. After writing some documentation to capture the knowledge, we called it a day.

EMC Support Note Odds and Ends

One thing that I realized when researching this issue was that the Support Note numbering system was about to break the 100,000 mark. I decided to find the first note with a 6-digit number. Using the URL format, https: //solutions.emc.com/emcsolutionview.asp?id=esg######, I started at 100,000 and on my fourth attempt, found the first PUBLIC note…

Support Note 100,003: Documentum Composer fails to install value assistance when the value assistance for a parent type attribute has been overridden. Written 25 September 2008, it outlines a bug that is fixed by upgrading Composer to 6.0 sp1. It isn’t a particularly useful note at this point, but worth commemorating.

I just hope I never see Support Note 1,000,000.

Include a time stamp with pings

Ross — Wed, 17 Jun 2009 15:46:20 +0000

It might be useful to include an absolute time stamp when pinging multiple hosts so as to be able to make a correspondance later on. This is what I put together in a hurry that does the trick.

while test 0; do  DATE=$( date | tr -d '\n' ); \
PING=$( ping -c 1 192.168.1.100 | grep from ); \
( echo $DATE $PING; sleep 1 ) | tee -a /path/to/log ; done

Got a better way to do this? Post a comment.

Auto Populate Time Stamp in SQL Server 2005 Express

khansalmanahmad — Mon, 08 Jun 2009 23:19:29 +0000

Recently I was experimenting with trying to modify a database by adding an auto-populating Time Stam

Connessione con HTTP Server

mmaggi75 — Fri, 29 May 2009 14:40:47 +0000

Oracle può essere utilizzato per effettuare una connessione HTTP: mi è capitato di affrontare un simile scenario quando ho dovuto “arricchire” dei dati a partire da informazioni che venivano erogate da un servizio di rete. Ho dovuto scrivere una routine Get_Stream() per recuperare l’XML dalla rete ed effettuare un parsing per estrarre i valori e caricarli nel database.




DECLARE


 
v_url VARCHAR2(255) := 'http://mysite.it:80';



v_clob CLOB;



v_size NUMBER;



v_time TIMESTAMP;



v_duration INTERVAL DAY TO SECOND;


BEGIN



DBMS_OUTPUT.put_line('Connessione HTTP = ' || v_url);



v_time := SYSTIMESTAMP;



PKG_UTILITY_HTTP.Get_Stream(v_url, v_clob);



v_duration := SYSTIMESTAMP - v_time;



v_size := DBMS_LOB.Getlength(v_clob);



DBMS_OUTPUT.put_line('Letti bytes ' || v_size || ' in ' || v_duration);


END;

L’apertura di una connessione TCP/IP verso un indirizzo esterno al database è un’operazione delicata, quindi non permessa di default. Eseguendo il codice precedente ci si può imbattere nell’eccezione:
ORA-29273: richiesta HTTP non riuscita ORA-06512: a "SYS.UTL_HTTP", line xxxx ORA-24247: accesso alla rete negato dalla lista di controllo dell'accesso (ACL) ORA-06512: a line xxxx
Bisogna dunque verificare che le Access Control Lists (ACL) del database consentano l’apertura di una connessione verso l’indirizzo ‘http://mysite.it’ sulla porta 80.
SELECT * FROM DBA_NETWORK_ACLS;

NOTE

La creazione/modifica di un’ACL può essere fatta solo da un utente con i privilegi DBA. Per maggiori informazioni consiglio gli articoli:
Fine-Grained Access to Network Services in Oracle Database 11g su oracle-base-com
DBMS_NETWORK_ACL_ADMIN su download.oracle.com
Quando ho incluso la procedura in un package, sono stato costretto a specificare la clausola AUTHID CURRENT_USER per poter utilizzare l’ACL precedentemente creata. Questo forza il package ad essere eseguito con i privilegi dell’utente effettivamente loggato e non con quelli dell’utente che ha creato il package.

Build Versioning Tip

Jason Lenny — Fri, 29 May 2009 14:18:08 +0000

One easy way to get more value out of your build system is to improve one of it’s fundamental outputs: the build number. Many of us have been using the basic major, minor, revision, increment format for years (I know I did!), but most build systems these days, especailly ones you’ve built yourself, can use any format you like. A good one that I’ve used in the past is the following:

Template: (Major).(Minor)_(Branch Name)_(Datestamp).(DailyIncrement)

Build Number: 3.4_Prod_20090529.3

Translation: Production Branch, 3.4 release, built on 05/29/09, was the third build of the day.

This provides a wealth of more information than the basic format. Just from seeing the build number you know when it was built, what major/minor release it is associated with, and what branch it was built out of. The only piece of information you’re losing versus the old method is the running total number of builds you’ve created since started the project, which is of questionable value anyway.

One issue you may run into if you are using Windows is that it expects the “File Version” value for assemblies to be in the 0,0,0,0 format. A good way to get around this is to put major, minor, date (with the year removed), and increment in that field and then use the “Product Version” field for your expanded build number. So, with the example above, you’d end up with a file version of 3.4.529.3 which works great with the file version field.

DECLARE
	v_url VARCHAR2(255) := 'http://mysite.it:80';
	v_clob CLOB;
	v_size NUMBER;
	v_time TIMESTAMP;
	v_duration INTERVAL DAY TO SECOND;
BEGIN
	DBMS_OUTPUT.put_line('Connessione HTTP = ' \|\| v_url);
	v_time := SYSTIMESTAMP;
	PKG_UTILITY_HTTP.Get_Stream(v_url, v_clob);
	v_duration := SYSTIMESTAMP - v_time;
	v_size := DBMS_LOB.Getlength(v_clob);
	DBMS_OUTPUT.put_line('Letti bytes ' \|\| v_size \|\| ' in ' \|\| v_duration);
END;