In my limited experience, the most likely reason those devices weren't created is that there is no driver matching your kernel, and the built-in scheme to build a driver failed. Even if your kernel is supported, you need a working gcc installation, and kernel sources installed,to enable the build.
Simply creating those devices won't take care of it. If the driver is correctly installed, changing permissions on the devices may be a way to work around problems with the vtune group membership.
A common problem in the past has been that available kernel sources didn't exactly match the running kernel.
Just yesterday, a procedure was posted along with the download which covers building the driver for one of the red hat EL3 versions, where the vtune driver build script was broken by changes in EL3 subsequent to vtune development.
Your latest posting shed some light! VTune 2.0 for Linux does not support RH EL 3.0, so it isn't possible for those particular sampling drivers to be created during the install, which explains the errors you're seeing.
If you examine the install.log that was created during your install, you should see some errors stored regarding that OS,that maybe flashed by too fast pm the display. (Something along the lines of, Hey, this is an unsupported OS, but do you want to continue to install anyway?)
Regardless, if you have a Windows workstation nearby, the VTune for Windows analyzer 7.1 supports data collection for Linux applications on RH EL 3.0 by means of a linux remote agent. If that might work for you, you can download an eval version of that VTune from: